Limits of hiragana-based romanisation about ichiran HOT 5 OPEN

Yeah, this sounds like a good idea. One problem though, in JMdict database hiragana readings are not separated by kanji so this wasn't possible to implement at the time I wrote romanization algorithm. More recently I have implemented a kanji module (kanji.lisp) that has a function match-readings that can potentially be used to resolve this issue.

from ichiran.

Oh. I didn't know that. I guess that makes what I had in mind quite difficult.

Special readings could be a problem. And then, what if (this is entirely fictional. I don't know if a real-world example exists) you have a word made up of two kanji, the first one could be read あ or あお and the latter can be read お or おう? If you only know that the entire word reads あおう, then that could be split into あ-おう or あお-う...

from ichiran.

I noticed that the traditional basic option on the site doesn't create the ō. I'm wondering @tshatrov , is there a way to change the romanization settings using ichiran-cli (I'm specifically interested in doing that using the -f option)?

from ichiran.

@tslater I think if you do (setf ichiran:*default-romanization-method* ichiran:*hepburn-basic*) before building the executable, then -f will use basic romanization.

from ichiran.

Looks like it is working. Thanks!

from ichiran.