Quote:
Originally Posted by Dave_S
It could be an encoding glitch. I have seen similar situations occur in other books where two different encodings were specified. CR3 just happened to use the wrong encoding of the two and ADE just happened to use the correct encoding. In that case, I think that the two competing encodings were WIN1252 and UTF8.
|
I've seen a problem in BAEN free epubs where the actual text in the epub's html within the epub is written to include smart quote and emdash characters not as escaped HTML.
These characters display fine in a web browser or SIGIL but appear as 3 hi-ascii like symbols including a TradeMark symbol in Coolreader on the android.
Coolreader does not handle this situation cleanly since the text becomes unreadable when trying to decipher what the text should actually be.
The same epub, read in FBReader, will display these characters properly without corruption making these EPUBs much easier to read in FBReader.
I raised a change request on Buggin's sourceforge project to get this situation handled better. I suspect the OP's issue is a similar one.
Not sure whether CR3 is more epub standards compliant than FBReader in this respect, but BAEN epubs are pretty widespread so I would hope that CR3 is eventually improved to display them better, even if BAEN epubs are not particularly standards compliant.
It's worth remembering that CR3 claims limited epub support not 'full' epub support on the Marketplace, I guess.