Cred că ADE ar trebui să se descurce cu un epub utf-8 fără să trebuiască să mai inserăm fonturile. Asta ața, la pretențile lui Adobe...
De altfel, de ce nu recunoaște diacriticele în "corpul " cărții dar le redă perfect în meniuri și etc?
Îți spun eu, programatori diferiți pentru interfață și rest și apoi au unit prost codul final.
Soluția ta e bună dar mă cam încurcă căci vreu să folosesc numai CALIBRE pentru toate conversiile...
Uite poza;
Uploaded with ImageShack.us
edit:
ePub and diacritics: a problem and a solution!
Believe me or not, there might be one more reason for Penguin Books to embed the Charis SIL font into their ePub books—other than making them look the way they want it to look on no matter what platform. The font is no big deal per se, and it’s not very popular in publishing, so I always wondered why are they embedding a typeface anyway.
Yesterday, I’ve just discovered «a bug that might be a feature» in Adobe Digital Editions (ADE).
As it’s well-known, the ePub file is a ZIP archive containing mostly (X)HTML files. Each and every XHTML file must be UTF-8 encoded, which should guarantee that, as long as you’re using a font that has all the required glyphs, your characters should display correctly in all the readers.
Well, this is not true for Adobe Digital Editions! No matter what font are you specifying (if none, the default fonts will be used), ISO 8859-1 (Latin-1) characters will be perfectly displayed (say, English, French, Spanish), but the non-Latin-1 characters would not!
For instance, Romanian and Polish specific characters will be displayed by ADE as question marks.
I have experienced this issue with ADE regardless of the fact that:
•the files were UTF-8 and correctly displayed in any browser and in ePub readers other than ADE;
•the fonts specified in the CSS were Unicode and available on the system (Palatino Linotype, Georgia, Cambria).
After a quick googling, I ran over a MobileRead forum thread, where people complained that Esperanto characters were not displayed…
If I’ve correctly understood, ADE does this idiocy on purpose, by using the following twisted logic:
1.ADE should display an ePub the same way on any platform: various e-readers, Windows, Mac.
2.On many e-readers, the default fonts are not Unicode; specifically, they support characters from a limited set of languages, but not all (say, Polish and Romanian are not supported).
3.Therefore, ADE should only support the same character codes as it does on those e-readers, regardless of the fact that on Windows and on Mac, the default system fonts are fully Unicode!
Let me detail you how this works in practice:
1.You specify in the CSS some font that should support your character set (say, Georgia, Cambria, Palatino Linotype).
2.ADE will use the specified font to render your ePub… but only for the subset of characters that would otherwise be supported on any e-reader that doesn’t have your specified font!
3.ADE will display ‘?’ instead of the non-Latin-1 characters you wanted, no matter the used font would have supported them.
Sheer idiocy.
Thanks to the above-mentioned thread on the Esperanto characters, and because I’ve peeked into their test ePub, I’ve found out that the correct workaround to this behavior is to embed into the ePub the fonts you will be using in your e-book! (Hint: How to embed fonts in ePub files.)
This is why, from now on, I’ll embed the Charis SIL font (four variations: regular, bold, italic, bold italic) in all the ePub files I’ll be building from now on, as long as I suspect that non-Latin-1 characters might appear in the text.
What a idiocy: I can’t just specify existing system fonts (which, BTW, I could also upload to my BeBook Mini), because Adobe Digital Editions is dumb by design!
The Charis SIL font comes under an open license, but the reason to choose it is that it’s used in most of the ePub files released by Penguin Books.
(de aici http://beranger.org/post/703998095/epub ... a-solution)
|
