it's entertaining how all of you have no shortage of opinions when it comes to any vague half-assed idea that gets floated. but i ask for concrete criticism on actual files you can look at, and nobody makes a peep. once again, so it's explicit to all that you have nothing to say: here's the test-suite:
here's the script that converts the test-suite into .html:
here's the .mobi version of the test-suite:
here's the .epub version of the test-suite:
here's the folder holding all of the conversion files:
here's a .zip file containing all of the conversion files:
*** what i have created is a transformation flow that gives an equivalence which spans across the entire workflow, so i can provide -- and even point you specifically to -- a particular chunk of text within a book as it exists: 1. in an abstract structural representation of the book; 2. as text, existing with a plain-ascii light-markup file; 3. as x/html (in a mix of flavors, from html3.2 to html5); 4. on the web in many forms (by page, chapter, book, etc.); 5. in a .mobi; 6. in an .epub; 7. in a .pdf; 8. in a web-app; 9. in an i.o.s. ipad/iphone app; 10. where all these formats can sync with online forums; 11. which forums could be for proofing, discussion, etc., 12. such that forums in #11 could circle back to point #2. maybe you don't understand this is a remarkable achievement. maybe you're not paying attention. if you _are_ paying attention, feel free to give me any feedback. otherwise, i'll assume you can't see any room for improvement... thank you. that is all. have a nice day. :+) -bowerbird