5 ms·
The way the "koma" is placed above 困っ makes me suspect they first tokenize the text, get furigana for each segment (most tokenizers have this built-in) and then
by yorwba 7y ago
The way the "koma" is placed above 困っ makes me suspect they first tokenize the text, get furigana for each segment (most tokenizers have this built-in) and then derive the romaji without correctly handling the sokuon っ when it appears just before a segmentation boundary. Usually it's represented in the romanization by doubling the following consonant, but of course that doesn't work if there's no following consonant because each token is treated as a separate string. They do get it right for "erikku" where there's no segmentation boundary.
- gryson 7y agoThat makes sense. Hopefully it can be fixed, since geminates are one of the most difficult features of Japanese pronunciation for native English speakers to master. Erasing it from the orthography intended to aid beginners certainly doesn't help.
- LinguaBrowse 7y agoIf they're having troubles with correct romaji transliteration (and even if not, to be honest), I don't see why they don't just transliterate it in furigana then. The source data of Tokeniser dictionaries such as NAIST JDIC isn't even in romaji, so if they are using a proper tokeniser, then they're actually doing an extra step and throwing away data to transform it into romaji form.
- yorwba 7y agoThe feature is probably targeted at absolute beginners who don't even know kana yet. The screenshot of the settings does show the option to select a different transliteration, but romaji seem to be the default.