View Single Post
Old 12-01-2022, 09:21 AM   #3
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,804
Karma: 6000000
Join Date: Nov 2009
Device: many
FWIW, under epub3, the nav does not have to be in the spine at all. You just need to not have the nav landmarks point to the nav itself as you can not include a non-spine item in the nav landmarks.

If you go that way the nav is treated exactly like the old ncx under epub2 and is not seen by the user as part of the text.


And if it helps, afaik CSS transform was added in CSS 1 and updated in CSS 2, so it should work properly in decent epub 2 readers even those using older Adobe Reader sdks.

Perhaps some readers bail on the css when they see the older platform specific versions in the css?

Last edited by KevinH; 12-01-2022 at 10:56 AM.
KevinH is offline   Reply With Quote