Quote:
Originally Posted by JSWolf
It would be best to make this program you are working on a plugin for the calibre editor and/or Sigil where is can show what needs to be edited be is removed or changed.
For something like KFX, it's only needed to be changed if it causes a problem or need to work, but doesn't. <section> is an example of something you can ignore as it doesn't make any difference when reading the eBook. It only makes a difference when coding.
|
Alas, I'm not a programmer. I wouldn't even know where to begin. However, I have dug up one MIT licensed resource ("
Word Up") that is
local and uses JavaScript to markup rich-text into actually clean HTML (no CSS mess; but preserving style markup that is otherwise blown-out via other suggested means of doing this, which totally
sucks) that would be great as a plugin 'conversion', but... it's piggybacking off of something else (CKEditor 4). I don't know if it could be made to function by itself in just a Calibre plugin. However, something like that (without the markdown option), is
sorely needed as such a resource as this. In the meantime, it'll be that and copy/paste (I have repackaged Word Up as a portable app).
Personally, I like
WordtoHTML better, but it isn't open source and there's some funky variant sever-side key preventing you from even looking at the full source code (JavaScript), so lol.
Anyway, yes, I'm attempting to make this resource (X)HTML5 compliant; semantically correct. Not <div> salad. It matters to assistive technology. If we're bothering, might as well be bothering to do it right and to current spec, I figure. (And, there is a valid argument in that it is easier to read and therefore to maintain; a nice plus).
Quote:
Originally Posted by JSWolf
Don't use % for margins. If you do, you get a different size margin for different size screens. I've seen a lot of eBooks from Amazon with a text indent of 7% witch is too large. And on a Kindle Scribe is even larger. I use a text indent of 1.2em and that looks good. Even if it changes with the font size change, it keeps it consistent based on the font size.
Also, don't make the chapter headers with so much wasted space. I've seen wasted space of 15% in some eBooks. Don't use %. Use em. 1em top/1em boom margins works well.
It sounds like Amazon's guidelines have some rather stupid stuff in there.
|
It's the only resource that bothers to (poorly) document what actually is supported or not at the code-level, so there's that. But, yes, this particular one stands out. And thank you for clarifying that, I suspected it was erroneous but wanted to make extra sure.