MobileRead Forums - View Single Post

DiapDealer · 01-14-2016, 08:24 AM

Put it this way: we love the idea of a trouble-free conversion of a Sigil created epub to a Kindlebook. We're not, however, likely to help accomodate the quirks of such a conversion when those quirks involve a deviation from the epub specifications.

In my opinion, any reading system that will render an entity (numeric, hex, or named) properly, but not its character representation is simply broken (epub or otherwise). Glyphs are glyphs.

Cases where neither the entity NOR the character will display are either a case of the system/reader font missing the necessary glyphs, or a case of character encoding conflicts. The former is out of our control, and the latter is something we will not tackle. Epub uses utf8/16. Period. Anything opened in Sigil will be forced into that particular character encoding box.

01-14-2016, 08:24 AM	#12
DiapDealer Grand Sorcerer Posts: 28,692 Karma: 205039118 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Put it this way: we love the idea of a trouble-free conversion of a Sigil created epub to a Kindlebook. We're not, however, likely to help accomodate the quirks of such a conversion when those quirks involve a deviation from the epub specifications. In my opinion, any reading system that will render an entity (numeric, hex, or named) properly, but not its character representation is simply broken (epub or otherwise). Glyphs are glyphs. Cases where neither the entity NOR the character will display are either a case of the system/reader font missing the necessary glyphs, or a case of character encoding conflicts. The former is out of our control, and the latter is something we will not tackle. Epub uses utf8/16. Period. Anything opened in Sigil will be forced into that particular character encoding box. Last edited by DiapDealer; 01-14-2016 at 08:32 AM.