View Single Post
Old 12-04-2013, 07:33 AM   #16
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by tshering View Post
I cannot see that davidfor says this. I take his statement as implying that he first had a certain suspicion in this direction. and did not found supporting evidence.
No, I was just eliminating possibilities.
Quote:
If the problem were related to the font, one would rather expect to see squares or question marks or empty spaces.

How can this explain that anacreon (Aura HD, FW ?), davidfor (Glo, FW 3.1.0) and I (Touch, FW 2.6.1) see the correctly interpreted characters, whereras fxp33 (Glo, FW ?) and I (Touch, FW 3.0.1) see the underlying UTF-8 code. As an additional information: fxp33's test file contains also a Chinese character that cannot be produced by combining characters.

I myself don't have any clue what might prevent the utf8 decoding on fxp33's and my reader.Maybe it is a side-effect of some entry in the configuration file?
It didn't work on my Touch with FW 3.0.1. So, I installed 3.1.0. It worked. That probably means a bug in the display code in 3.0.1 that was fixed in 3.1.0.
davidfor is offline   Reply With Quote