Quote:
Originally Posted by man2010
Why does Sigil have to convert all codes and entities into symbols in the code view?
|
Because Gumbo (the Sigil html parsing engine) does not grok entities. You can, however, enter a list of entities you wish to preserve in the Preserve Entities preferences (Edit->Preferences->Preserve Entities).
As for some sort of warning that an epub is not 100% ready to be converted to a Kindlebook ... that's just not going to be an integral feature of Sigil. Someone could write a validation plugin that could check for common kindle conversion bug-bears, though. There could even be an output plugin that fixes some of those bugbears. In fact; almost all of the points you raise sound like perfect examples of where plugins can come the rescue.
Quote:
Originally Posted by man2010
Sigil usually converts the code of Unicode symbols into symbols themselves in UTF-8 files (when you import an HTML file into Sigil); later, when you try to convert such an EPUB file to Kindle, these symbols may get mangled.
|
I guess I'd need to see some specific examples of where/when this "mangling" occurs. Because if a Kindle can properly display the numerical/named entity, then it should have absolutely no problem displaying the character it represents. Either the necessary glyph is included in the Kindle's fonts, or they're not. I fail to see how Sigil's conversion of entities to characters can be the cause of any improper Kindle rendering. But again... you could always preserve a list entities that you deem to be problematic on Kindles if you like--though it's my contention that as far as Kindles go: what's good for the entity is good for the char. Numerical or named entities don't magically create renderable glyphs out of thin air, after all.