View Single Post
Old 11-30-2015, 02:54 PM   #166
dickloraine
Guru
dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.dickloraine ought to be getting tired of karma fortunes by now.
 
Posts: 631
Karma: 7544528
Join Date: Apr 2013
Location: Berlin
Device: PRS 350, Kobo Aura
Quote:
Originally Posted by Sarmat89 View Post
The problem is that it is unrealistic to expect various software vendors to support all the features of CSS (even the simplest features like text-transform are often missing). Because they are superfluous for 90% of books here, the CSS styling should add to the book format, not define it.
For that purpose, the format should be built on a semantic basis. The only kind of span we can allow is for xml:lang attribute, for the correct hyphenation.
I shure as hell expect for example a browser to support all features it needs to render websites. I exspect Microsoft to support all the features of a docx. A bad software is bad software. Let's just only allow markdown for ebooks, we don't want to make it to hard for the poor companies wanting to make readers. That way, even I could probably write a reader
dickloraine is offline   Reply With Quote