> I think it is not related to the text encoding, because I
> just run the fltk demo application in arm board, the text are
> all english letter.
OK - but English (i.e. nominally basic ASCII) text encoded as UTF-16
produces exactly the effect you describe, which is why I asked the
question...
E.g. what should be "Hello" - 0x48 0x65 0x6c 0x6c 0x6f in ASCII (or
UTF-8) becomes
0x00 0x48 0x00 0x65 0x00 0x6c 0x00 0x6c 0x00 0x6f in UTF-16... Which
would produce the empty glyphs you report.
> I have tried by using fltk-2.0, it has no
> such issue.
OK. No idea then. Sorry...
Only thing I can suggest is that you run "od" or "hexdump" on your input
text so that we can get a look at the raw binary, see how that looks...
od -t x1 my_file | head
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
