MobileRead Forums - View Single Post - [Plugin] ePub3-itizer

Fedwin · 03-19-2015, 05:16 PM

Thanks for this plugin. I am loving it!

One thing I noticed is that the nav that gets created doesn't remove the styling from the ordered list. I've been adding a link to the stylesheet and then adding this to the stylesheet:

ol {
list-style-type: none;
}

http://www.idpf.org/epub/301/spec/ep...-nav-def-model

›2.2.4.1 The nav Element: Restrictions

› The ol element represents an ordered list. In the context of this specification, the default display style of list items must be equivalent to CSS list-style: none (Reading Systems with no CSS support must not show list item numbering). Authors may specify alternative list item styles using CSS, but these would obviously be ignored by Reading Systems that do not support Cascading Style Sheets.

I also end up manually changing the links to the original toc.xhtml to link the nav.xhtml file, since I always delete the toc.xhtml and leave the toc.ncx.

I have no idea if it is possible, desirable, or practical to automate these things or if you have any interest in doing so if it is. I just mention it so that an incredible plugin could be ever so slightly more so.

Thanks again. I am very happy that Sigil and this plugin exist.

03-19-2015, 05:16 PM	#50
Fedwin Enthusiast Posts: 28 Karma: 10 Join Date: Dec 2011 Device: PRS-T1	Thanks for this plugin. I am loving it! One thing I noticed is that the nav that gets created doesn't remove the styling from the ordered list. I've been adding a link to the stylesheet and then adding this to the stylesheet: ol { list-style-type: none; } http://www.idpf.org/epub/301/spec/ep...-nav-def-model ›2.2.4.1 The nav Element: Restrictions › The ol element represents an ordered list. In the context of this specification, the default display style of list items must be equivalent to CSS list-style: none (Reading Systems with no CSS support must not show list item numbering). Authors may specify alternative list item styles using CSS, but these would obviously be ignored by Reading Systems that do not support Cascading Style Sheets. I also end up manually changing the links to the original toc.xhtml to link the nav.xhtml file, since I always delete the toc.xhtml and leave the toc.ncx. I have no idea if it is possible, desirable, or practical to automate these things or if you have any interest in doing so if it is. I just mention it so that an incredible plugin could be ever so slightly more so. Thanks again. I am very happy that Sigil and this plugin exist.