Rei,
> I found some characters are missing:
If there are characters missing, just take out the following line from the fontforge script:
----
# select lesser range of glyphs
SelectMore(0u0020,0uffee)
SelectInvert()
Clear()
SelectNone()
----
> I think convert otf font to ttf maybe no a good idea
I think the problem is just that we shouldn't cut characters from the font until we know what we are cutting. I think the conversion from otf is working fine (well, there might be some side effects, but it isn't causing the missing glyphs).
These lines are cutting characters out of the font in an attempt to reduce the file size a bit. It's not necessary to do so.
> DroidSansFallbackFull.ttf is using in Ubuntu and old versions Android for cjk, it look acceptable in my document.
Yes, this is safe and indeed was my intention to have this supported in Asciidoctor PDF since PDF requires that you specify a font for every character (unlike a web browser). I saw your pull request, so I'll test that and merge it in. Thanks!
> I found English and Japaness support (in the M+ font), no Chinese and Korea, am I missing something?
I think the website is outdated. If you clone the repository, then you should see that you get all the characters. They are also packaged for Fedora and Ubuntu, so you can get them that way (see
).
> The perfect solution is directly support otf font in prawn, than editor
can use the best font for his/her document, but I don't know how to
write a otf parse for prawn.