Just to pick nits:
Quote:
Originally Posted by Hitch
[*]Amazon, B&N, Kobo and Apple all have self-publishing portals. There are other self-publishing portals (Smashwords, et al) being used around the world. All of these--ALL--basically work off of Word or, in Apple's case, Pages (via iAuthor). NONE of these word-process programs have remotely decent XML export capabilities.
|
Actually, all of those word processors store all of their content in XML format at this point (at least for new Word files, and for every version of Pages ever). What I think you mean is that their XML isn't semantic, and is vastly too complicated to convert sanely to EPUB or other publishing-related XML dialects without throwing a lot of information away.
Quote:
Originally Posted by Hitch
Anyone who thinks it MIGHT be should look here: http://www.docbook.org/tdg5/en/html/ch02.html . And while the OP can say that his idea is NOT DocBook--it IS DocBook. Or, if not exactly DocBook, it's DocBooks' kissing cousin, for all intents and purposes. |
FYI, I author my fiction books in DocBook now. But then, I'm a programmer, and I wrote my own tools to translate that into EPUB (and PDF via LaTeX), so I'm the exception that proves the rule.
Maybe if I can fix a couple of the remaining crasher bugs in WebKit's HTML editing, I might make my XML editor available to the general public, but right now, it crashes way too often. Still, it makes writing XML a lot easier than vi.