In Spanish, readlang lets you click a single word as one unit. In Japanese, I’m seeing that every single character is a distinct word, and I have to drag the mouse across multiple characters to form a complete word.
I understand this might afford more flexibility but it’s extra mechanical effort to read. Is this something I am doing wrong, am I meant to configure readlang differently, enable a feature? Or am I philosophically incompatible with readlang? That’s fine if so, just would be nice to understand the intended usage.
The honest answer is that because I’m not learning Japanese myself, and because I’ve prioritized improvements which benefit all languages, I haven’t put the effort into understanding how to automatically split Japanese sentences into “words”. From listening to user feedback it seems to me that for better Japanese support Readlang should both:
Automatically detect word boundaries
Provide transliteration support (into romaji and conversion of kanji into hiragana)
Hopefully one day I’ll get around to these. In the meantime you need to manually select the range of characters to translate yourself.
Thank you for the quick response. This makes sense, and I agree with the user feedback as you described it. I have heard that either AI tools or “MeCab” are good options for word splitting.