Closed GoogleCodeExporter closed 8 years ago
AnyMemo is able to display unicode character as long as you use UTF-8.
If you import the csv / txt, you must choose "UTF-8" as encoding. If you are
using Windows, you can open you csv / txt in Notepad and "save as" and choose
encoding as "UTF-8".
If that is not the case, please let me know by replying this issue.
Original comment by mrlhwlib...@gmail.com
on 14 Sep 2014 at 4:52
Thank you for your advice. I have tried this and still cannot see any
characters in the range 1F00-1FFF, only small hollow squares. The import
works, but these characters do not display in AnyMemo on my HTC One (M7),
running OS 4.1.2. However when I view the database on my Windows 8
computer, using SQLiteStudio (v2.1.5) I can see all these characters
correctly, so perhaps the problem is an incomplete Unicode font on my HTC.
For comparison I have downloaded several existing (and presumably tested)
ancient Greek flashcard sets from the AnyMemo site, and get the same
problem for them all: Languages - Greek => Ancient Greek - Core Vocab,
Greek Morphology, Metzger Vocab Lists. Any characters such as
ὐῖῶἐὅἥὅὗὕἔἵὁἀ do not display in AnyMemo on my HTC. I
see similar behavior
on an HTC One X, except there are no boxes, just blank spaces for these
characters.
Any further ideas would be appreciated.
Original comment by caviness...@gmail.com
on 20 Sep 2014 at 9:32
If small squares are shown instead of the real characters, it means your
phone's font does not contain that character. I think other apps cannot display
them either.
There is one function you can try out. In the db settings, you can use
"User-defined font". Copy the .ttf font file to your phone's external storage
and then you set the font file. Double click on the empty field for user
defined font, you can select the .ttf file. This might work for you.
Original comment by mrlhwlib...@gmail.com
on 20 Sep 2014 at 9:50
Beautiful! That works perfectly. Thank you so much for your help.
Original comment by caviness...@gmail.com
on 20 Sep 2014 at 11:07
Original issue reported on code.google.com by
caviness...@gmail.com
on 14 Sep 2014 at 1:34