I'm more interested in (kind of) the reverse. Given a Japanese sentence (that uses kanji), figure out the proper reading for each Kanji character, using a neutral network. I know there are already hardcoded analyzers, like kuromoji, but they produce incorrect answers in a lot of edge cases.
Show HN: Neural Japanese Transliteration
41–50 of 55 posts
Re: Show HN: Neural Japanese Transliteration
#42> In the digital environment, people mostly type Roman alphabet Might be selection bias but I mostly notice people using the 10-key click one
Re: Show HN: Neural Japanese Transliteration
#43Earlier quoted context omitted.
For what it's worth, this is basically just the same as any popular Japanese (or Chinese) input method. Usually the approach is to greedily form the smallest set of the longest words from the given syllables, because people tend to give inputs where all the words are complete. Sometimes people use markov models to fix situations where that falls over. Not sure how well this model performs, but the task is not novel.…
Spoken Japanese isn't any more ambiguous than English (for a human, or a speech-to-text AI) because Japanese people pause between spoken words just like anyone else. But a stream of romaji furigana with no spaces is quite ambiguous—since there's nothing to indicate word boundaries, any substring of the input might turn out to have actually intended to be e.g. a katakana spelling of a name. If CJK IMEs expected and re…
Re: Show HN: Neural Japanese Transliteration
#44Earlier quoted context omitted.
For what it's worth, this is basically just the same as any popular Japanese (or Chinese) input method. Usually the approach is to greedily form the smallest set of the longest words from the given syllables, because people tend to give inputs where all the words are complete. Sometimes people use markov models to fix situations where that falls over. Not sure how well this model performs, but the task is not novel.…
Spoken Japanese isn't any more ambiguous than English (for a human, or a speech-to-text AI) because Japanese people pause between spoken words just like anyone else. But a stream of romaji furigana with no spaces is quite ambiguous—since there's nothing to indicate word boundaries, any substring of the input might turn out to have actually intended to be e.g. a katakana spelling of a name. If CJK IMEs expected and re…
The Japanese disambiguate word boundaries in spoken language using the pitch accent as the primary clue. Tokyo Japanese has a phenomenon called initial rise, which differentiates the pitch between the two first moras of an accent phrase – either the pitch rises or steeply falls.
Here's an example - upper case: high pitch, lower case: low pitch.
KYOu, kaINI iKIMAshita
today, to buy I went
KYOu KAini iKIMAshita
today, to meeting I went
kyoUKAINI iKIMAshita
to chuckh I wentRe: Show HN: Neural Japanese Transliteration
#45Earlier quoted context omitted.
> Spoken Japanese isn't any more ambiguous than English (for a human, or a speech-to-text AI) because Japanese people pause between spoken words just like anyone else. Also intonation, which is not captured by the written system at all. Japanese isn't strongly tonal in the way Chinese is, but it has a regional prosody, like Swedish, which helps in disambiguating meaning.
It’s usually analysed as having both normal prosody and a pitch accent (similar to a stress accent) that varies somewhat by region. I’ve read that broadcasters are expected to use a standard (Tokyo?) pitch accent when speaking.
Re: Show HN: Neural Japanese Transliteration
#46Anybody familiar with the history of this project?
Re: Show HN: Neural Japanese Transliteration
#47I'm more interested in (kind of) the reverse. Given a Japanese sentence (that uses kanji), figure out the proper reading for each Kanji character, using a neutral network. I know there are already hardcoded analyzers, like kuromoji, but they produce incorrect answers in a lot of edge cases.
its very hard to do that since there are cases when you can read the kanji In multiple ways, like In peoples names for examples. Japanese is full of exceptions because the writing system was imported very, very late In Japan (300ad) without much effort to standardize its application.
The kanji -> kana direction should be considerably easier than the kana -> kanji direction. There are many fewer sources of ambiguity, and the space of possible answers is smaller.
Re: Show HN: Neural Japanese Transliteration
#48> In the digital environment, people mostly type Roman alphabet Might be selection bias but I mostly notice people using the 10-key click one
except in asia. Koreans and Japanese use a lot of dial type input systems.
Re: Show HN: Neural Japanese Transliteration
#49> In the digital environment, people mostly type Roman alphabet Might be selection bias but I mostly notice people using the 10-key click one
True on the smartphone. On the computer most Japanese speakers I know just type romaji. However, this is pretty much irrelevant to this article, as romaji->kanas (the phonetic alphabets) is a pretty straightforward and solved problem (there is a clear bijection between both). The real problem is transforming the phonetic transliteration into the correct word in either kanji (for most Japanese words) or katakana (for…
Re: Show HN: Neural Japanese Transliteration
#50I feel like I've read that readme file a few 2-3 years ago, but everything says 14 hours ago. Anybody familiar with the history of this project?