Quote:
Originally Posted by eschwartz
How is your proposed format a predictable experience, if you still cannot explain to us what the specs are for your proposed format?
|
I thought I was explicit about the staples:
- OpenContainer Format
- XML-based metadata with specific, machine-readable format for genres, keywords, series, contributors, with predefined contributor roles applicable for the illustrated books.
- XML-based semantic markup for the book texts, with CSS support but no generic elements such as <span> and <div>. There is a hierarchic section structure for books, chapters, prefaces, forewords, etc. All formatting such as italic and headings is done by specific elements. There is native support for footnotes, endnotes, images as out-of-text, in-text, in-line. There are semantic classes for dedications, epigraphs, poems, scenic directions, quotations, messages, etc. There is an automated TOC building with the possibility of customization.
- All not essential features like fonts, paragraph indents, drop caps are not supported and should be provided by the reader app or optional CSS.
Quote:
|
And I asked, which other readers?
|
Coolreader desktop, Coolreader Linux (on a device), and Coolreader for Android.
Do you need a list of those that had loaded the file but shew the poem wrong too?