View Single Post
Old 12-04-2013, 05:49 AM   #15
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by Leonatus View Post
Maybe, it depends on the used fonts, as davidfor says.
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. If the problem were related to the font, one would rather expect to see squares or question marks or empty spaces.
Quote:
Originally Posted by Leonatus View Post
Most likely your display issues are caused by these and other combining characters. Try replacing them with combined characters.
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?

Last edited by tshering; 12-04-2013 at 06:03 AM.
tshering is offline   Reply With Quote