I think this is a symptom of Android having a Chinese font by default.
Unicode is somewhat broken in that instead of making separate
code-points for the Chinese and Japanese versions of the different
characters, they decided to put them both on the same code-point and
let the application figure out whether it was displaying Chinese or
Japanese and choose the appropriate font (I don't really know why this
was considered a good idea, perhaps because it let them fit everything
into 16-bit).
Ways to fix this:
1 Root your phone and install a Japanese font instead
(DroidSansJapanese.ttf is available in the Android SDK). This is
technical but will fix all of your apps in one go.
2 Ship a Japanese font with Aedict - this will increase the size of
the download by about 1MB.
3 Allow the user to change the font, then get them to copy a .ttf to
the sdcard and point aedict at it (this makes life a bit harder for
users).
http://code.google.com/p/ankidroid/wiki/Installation
has some discussion about this topic related to AnkiDroid,
F
Hi,
I'm not that far in japanese learning but my (japanese) wife pointed out the same mistakes.
The truth is nor Aedict nor JED are wrong ... they simply use a bad file : kanjidic
So the developers are not to blame in this case. I searched for another opensource kanji file to post it but couldn't find a sole ...
Is there someone to rewrite it?
Rooting is not a practical solution for most people, I just mentioned
it for completeness.
Assuming fonts really are the problem, any proper fix will need a
change to Aedict to allow selecting a different font,
F
I was considering packaging the DroidSansJapanese font file in an
"app" that does nothing at all except deposit that file somewhere that
other apps can find it. Not sure if I'll find time to do that,
F
> Jim