View Single Post
Old 05-08-2013, 04:27 AM   #75
Manolo
Addict
Manolo has learned how to read e-booksManolo has learned how to read e-booksManolo has learned how to read e-booksManolo has learned how to read e-booksManolo has learned how to read e-booksManolo has learned how to read e-booksManolo has learned how to read e-books
 
Manolo's Avatar
 
Posts: 207
Karma: 792
Join Date: Dec 2012
Location: Spain
Device: Kobo AuraH2O & Onyx i62HD & M92
Quote:
Originally Posted by Clark G. Flipper View Post
Thanks for the hint, Manolo.
It turned out that the ebook contained a stylesheet and its own fonts. I deleted both. It messed up my ebook a bit, but after that the accented characters were displayed correctly.
Good. You could solve it.
While not strictly a CR or FBR bug is an important issue not having the option to disable stylesheet or fonts in an EPUB. I understand being unable to do that in PDF but not in EPUB.
In CR for Android you can disable CSS, what is more useful than having to go to the PC and edit EPUB file with Sigil or whatever ....
CR and FBR lack of options compared to their Android siblings is a disadvantage.

The other issue: how is possible having fonts that doesn´t support Unicode? Some font families as DejaVu have a quite good Unicode support but others don't.
Well, I can understand some fonts not having support of some not so used characters and some Unicode blocks not being fully implemented as "Unified Canadian Aboriginal Syllabics" or "Phonetic Extensions" because I think are not so used. But at least the first Unicode blocks should be implimented. I think that only implementing the fist two blocks (apart from ANSI of course) "Latin-1 Supplement" (rest of 8859-1 to support French, German, Spanish, Italian ...) and "Latin Extended-A" (adding support to Czech, Polish ...) we have many languages supported.

Last edited by Manolo; 05-08-2013 at 05:20 AM.
Manolo is offline   Reply With Quote