Module talk:th
Latest comment: 9 months ago by Atitarev in topic ฿ in transliterations
Unsuccessful romanizations
edit@Wyang: There are some module errors in Thai entries because of unsuccessful generation of romanizations, for instance in กินี-บิสเซา. It would be best to revert changing tracking to an error message and have the function just not display a romanization, unless there is some action that editors are supposed to take to fix the problem. — Eru·tuon 08:57, 16 September 2017 (UTC)
- I've fixed the errors and also added explanation for the message. IMO The error is warranted, since it catches 1) inappropriate usages of the template, 2) improvements to be made in the template/module, and both cases should be attended to ASAP. Wyang (talk) 09:55, 16 September 2017 (UTC)
฿ in transliterations
edit@Benwing2: Hi.
Currently, the module can't transliterate ฿ symbol correctly. I made it "bàat" but don't rem but it's not right. 500บาท(500 bàat) is correct but 500฿(500 bàat) should just produce "500฿" in the transliteration. It's a minor issue. Anatoli T. (обсудить/вклад) 00:21, 30 November 2023 (UTC)
- @Atitarev Hi, it's because there's a pronunciation entry for ฿ for Thai that gives its pronunciation as the Thai respelling of bàat. I'm not sure what the best solution is; I'll think about it. Benwing2 (talk) 00:26, 30 November 2023 (UTC)
- @Benwing2: Ah, thanks. I forgot what I did to make, at least to transliterate something. I deliberately added the pronunciation entry, since it would just fail, even if it works fine with e.g. $500($ 500) (although there is an unnecessary space between $ and 5). Anatoli T. (обсудить/вклад) 00:31, 30 November 2023 (UTC)
- @Atitarev I am starting work on the scraping transliteration code and I will see about fixing unnecessary spaces and stuff like that. Benwing2 (talk) 01:22, 30 November 2023 (UTC)
- @Benwing2: Thank you! At ไทย (tai), you can find longer quotations with respellings. They are also good as test cases. Along with User:Atitarev/Thai translit test cases or any other like ผมพูดไทยไม่ได้ ― pǒm pûut tai mâi dâai ― I don't speak Thai. Anatoli T. (обсудить/вклад) 01:27, 30 November 2023 (UTC)
- @Atitarev Thanks! One thing we could do is add a param to
{{th-pron}}
to indicate how to transliterate a term if the respelling shouldn't be used for this purpose. Benwing2 (talk) 07:31, 30 November 2023 (UTC)- @Benwing2: I'ts probably fine, as long as it doesn't break anything for
{{th-pron}}
but please give an example of what you mean. - Before I added a Thai entry to ฿, the translit just failed at Module:th#236 (with # I want to indicate the line number). That's the only reason I made a Thai entry. If the issue is fixed, the Translingual section is sufficient, ฿ doesn't really require a respelling or IPA. Anatoli T. (обсудить/вклад) 07:46, 30 November 2023 (UTC)
- @Benwing2: You can experiment and delete the Thai entry or
{{th-pron}}
there and make it transliterate the symbol error-free, like numbers or $ sign. Anatoli T. (обсудить/вклад) 07:48, 30 November 2023 (UTC)- @Atitarev I'm thinking something like
{{th-pron|บาด|translit=#}}
or{{th-pron|pron=บาด}}
or something that indicates that the respelling is only for pronunciation and that transliteration should use the pagename itself. Benwing2 (talk) 08:16, 30 November 2023 (UTC)- BTW I think the way you indicate a line number is like this: Module:th#L-236. Benwing2 (talk) 08:18, 30 November 2023 (UTC)
- @Atitarev Also, I think the reason that the translit failed is that the bhat sign ฿ is within the Unicode Thai block range (see [1]) and there isn't special casing for it. I may need to add that special-casing. Benwing2 (talk) 08:22, 30 November 2023 (UTC)
- @Benwing2: Thanks, I see now why it fails but not sure I can fix it myself. Anatoli T. (обсудить/вклад) 09:38, 30 November 2023 (UTC)
- @Atitarev Hi, where was our discussion about the Thai repeat sign and what is the default? Is it to repeat the preceding space-separated word (assuming Thai words are written with spaces separating)? Benwing2 (talk) 10:22, 30 November 2023 (UTC)
- @Benwing2: At User talk:Atitarev/Thai translit test cases, look for "ๆ". The current template repeats the previous space-separated word. It doesn't work correctly if there are more than one word. Anatoli T. (обсудить/вклад) 10:27, 30 November 2023 (UTC)
- @Atitarev Hi, where was our discussion about the Thai repeat sign and what is the default? Is it to repeat the preceding space-separated word (assuming Thai words are written with spaces separating)? Benwing2 (talk) 10:22, 30 November 2023 (UTC)
- @Benwing2: Thanks, I see now why it fails but not sure I can fix it myself. Anatoli T. (обсудить/вклад) 09:38, 30 November 2023 (UTC)
- @Atitarev Also, I think the reason that the translit failed is that the bhat sign ฿ is within the Unicode Thai block range (see [1]) and there isn't special casing for it. I may need to add that special-casing. Benwing2 (talk) 08:22, 30 November 2023 (UTC)
- BTW I think the way you indicate a line number is like this: Module:th#L-236. Benwing2 (talk) 08:18, 30 November 2023 (UTC)
- @Atitarev I'm thinking something like
- @Benwing2: You can experiment and delete the Thai entry or
- @Benwing2: I'ts probably fine, as long as it doesn't break anything for
- @Atitarev Thanks! One thing we could do is add a param to
- @Benwing2: Thank you! At ไทย (tai), you can find longer quotations with respellings. They are also good as test cases. Along with User:Atitarev/Thai translit test cases or any other like ผมพูดไทยไม่ได้ ― pǒm pûut tai mâi dâai ― I don't speak Thai. Anatoli T. (обсудить/вклад) 01:27, 30 November 2023 (UTC)
- @Atitarev I am starting work on the scraping transliteration code and I will see about fixing unnecessary spaces and stuff like that. Benwing2 (talk) 01:22, 30 November 2023 (UTC)
- @Benwing2: Ah, thanks. I forgot what I did to make, at least to transliterate something. I deliberately added the pronunciation entry, since it would just fail, even if it works fine with e.g. $500($ 500) (although there is an unnecessary space between $ and 5). Anatoli T. (обсудить/вклад) 00:31, 30 November 2023 (UTC)