Quote:
|
Originally Posted by Hadrien
No one's working on including HTML support, it's mostly about new XML based format these days, something much more specialized for e-books in this case. There's a lot of issues with HTML standardization these days, just take a look how web browsers support and render HTML in different ways. The real goal here is not only to create a standard for viewing e-books, but also something really easy to process. If the core of your format is based only on formatting like HTML, you won't be able to extract information or customize your book as easily. It's much easier to pull and filter out information from RSS for example.
|
I can appreciate that your comments come from a depth of understanding I do not have. You are probably right in what you advocate, but my comfort level about reader compatibility would be greatly increased if they would include an HTML rendering engine. I would hope they would standardize on the same one. Then I could use a lot of my current files. I could mark-up my txt files to give me the text appearance I want, and I could at least have a horizontal rule between chapters. It is not a difficult thing to do, and it would solve so many problems. I would like the rendering engine to be in the reader of course. One could even use it to display plain text.
I like the comments to the effect that we need to draw our text from a database and include markup for the things that make the text more readable. We need an easy way to massage and store the great mass of material we already have. HTML does all that and most people understand it.
So can we do both?