![]() ![]() If I understand correctly, they usually refer to smaller rivers than, or tributaries of maenam. Some rivers in Northern Thailand are traditionally prefixed with nam mae, e.g. น้ำแม่ ( nam mae) is a regional variant of the usual maenam river name prefix. It’s not, although Thais themselves barely use the term any more. At least according to my native speaking girlfriend. So use common sense to enter the name:en. Most people talk about going to “Wat Pho”, not to “Pho temple”. It happens that often the transliteration is more common than the translation. In case something had to be special handled there was the suggestion to use name:th-Latn I discussed this with Sven Geggus at one of the Hack weekends at Geofabrik. This can be done for example at the rendering step. ![]() We should avoid large-scale insertion of automatically generated transliteration. Transliteration should be avoided, but sometimes it is worth adding it. A good example is Bangkok instead of Krungthep. Name:en should be the English name when there exists an established one. This understanding complies which what is summarized about RTGS in the wikipedia:Ĭompounds and names of persons are written without spaces between words As Maenam is a single noun I would not split it into syllables. I consider it quite useful to use the text-to-speech engine which comes with it. It might give a hint what something is, but can also be horribly wrong. Do NOT use Google translate for translation of Thai names. The use of Nam Mae and Mae Nam or Maenam is a perfect example because they’re all (approximately) correct. I think we should avoid using Anglo-centric terms and stick to the proper Thai transliterations. When one is searching for a particular place or feature having multiple ways to spell it makes things difficult. It wouldn’t be such a big deal if it were consistent but it’s not. Many river names are likewise entered as, for example, Wang River rather than the more proper Mae Wang. But the spoken Thai sounds very good.īut to carry on the conversation a little further: The practice of using English words instead of the Thai transliteration is a common practice on OSM, Examples abound: Instead of Thanon Chotana for name:en we write Chotana Road. Some of the results are laughable and barely resemble what was being said. I’m sure it would help us all better understand how they are Despite your earlier recommendation, I usually avoid Google Translate because of the horrible job it does when translating Thai into English. Are Nam Mae and Mae Nam equivalent or is one more correct than the other? Why in some cases does the Thai Romanization program combine syllables, as in Maenam Huai Bong? And finally, which is the correct version of the name of the river that flows through Lamphun so I can at least tag all parts of it consistently?īut I’m hoping for a general comment from a native Thai speaker concerning such names. The original mapper translated it differently and got Nam Mae Kuang. Another portion of the river was tagged with this name: น้ำแม่กวง, which the Thai-Romanization program transliterates to Nam Mae Kwong. One road sign I photographed clearly shows this: แม่น้ำกวง, which my Thai Romanization program (Thai Romanization v1.5.2) shows as Maenam Kwong. I’m trying to determine the correct English translation for the name of the river that flows through Lamphun. Which brings me to the reason for asking about this in the first place. In some cases the signs indicate one way of arranging these common prefixes, while another sign shows another. Some names use two or more, some even use all four. The Thai names for these streams and rivers are often prefixed with either แม่ (mae), น้ำ (nam), ลำ (lam) or ห้วย (huai). I’ve been working on adding water features to OSM since discovering that many bridges in Chiang Mai province display the waterway’s name on highway bridges.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |