The simulator, but NOT the code deployed on android or ios, has serious deficiencies displaying unicode characters. The simulator uses AWT components, which have this deficiency throughout. I haven't surveyed exactly which components the simulator uses which have this weakness, but it includes com.codename1.ui.List
I don't recall seeing this mentioned. I suppose fixing it would be time consuming and overall low priority, but there ought to be a note somewhere to save developers a lot of time chasing phantoms when the simulator displays ◻◻◻◻ instead of Japanese strings. Note that if the simulator displays other garbage instead of blocks, you probably have a real problem instead of a fake, simulator-only problem. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/f1edf7e6-b166-4e71-bdad-4e6609c6f48f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
