View Single Post
Old 07-02-2009, 11:22 PM   #50
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Awesome link. I'm now reading about the boom microformat that page linked to. I may have to add elements!

I think that the reason I'm not doing the .epub thing is that it is so complex. I mean, no individual piece is complex, but altogether it's difficult to encompass. I don't like it when books are broken into multiple parts. If I want to edit an error, or change the layout in an EPUB it is unnecessarily complicated, I find. Just imagine changing chapter headings in it. How many documents might you have to open? Ridiculous. It's a web of interrelated documents, TOC, OPF, multiple chapters, size-breaks for readers, obsolescent folder structures, etc.

Making an OPF and EPUB from this should be trivial, for someone familiar with it. I am not an expert at HTML, XHTML or EPUB, OPF etc. Just trying to make something that is transparent, simple and transformable with minimal fuss.

The Dublin Core names for the meta-elements is probably something that I should do. But again, I find that DC is obscure at points (contributor, etc.) and I lean away.

This is all ground trod before, (DocBook, FB2, boom, etc.) but I can't help myself -- if I can make something lean and intuitively readable and editable, I'll be pleased. I want an archive format that doesn't require multiple steps to access and edit, or knowledge beyond basic XHTML/CSS. Hopefully it will carry its own "documentation" within it.

Plus, it's something to do.

m a r
rogue_ronin is offline   Reply With Quote