Quote:
Originally Posted by eschwartz
And what about my point, that you are doinng precisely what you profess to dislike every time you convert HTML to ODT and read it in LibreOffice...
|
I'm utterly confused by the whole discussion. We edit ePUBs in NoteTab Pro all the time. What's the difficulty?
An ePUB
is an htmlz file, for all intents and purposes. It's a bunch of html files (or one, if you want to deal with the size, and make a book that people can't read on some readers), with a nav TOC that *can* be made auto-magically by either Sigil or Calibre (or Atlantis, whatever); an OPF, to tell it what's where, and an NCX, ditto. Both of which not only can, but MUST, be made/edited in a text editor, or a dedicated ePUB-maker like Sigil.
Honestly, there must be something else here that I'm missing, because there's just nothing complex about an ePUB. AT its simplest, one HTML file; a nav TOC if you want one; an NCX for device nav, and and OPF, so the device knoweth where stuff IS. What's complicated about that, really? The OPF and NCX, versus using HTMLZ? Everything else is exactly the same, and if you use Sigil, you can plop your HTML file in there, and if you've used header styles (h1-6), it will build everything that you consider "complicated" FOR you.
I think, push-comes-to-shove, that if you're keen on text editors, I'd rather be dealing with an ePUB, than Word or ODT, quite honestly. ePUB, at its heart, is
all about the HTML. Hell, it IS a zipped-up webpage; it simply uses the NCX and OPF in lieu of a website's on-page menu, for navigation and structure. {shrug}
Sorry to join in with the thread-jack. But it's just oddball to me.
Hitch