Am 17.02.2012 um 12:44 schrieb Hans Hagen:
On 17-2-2012 10:42, Wolfgang Schuster wrote:
Am 16.02.2012 um 22:53 schrieb Hans Hagen:
On 16-2-2012 20:38, Aditya Mahajan wrote:
I do agree if the export tags were configurable. Something similar to multi-lingual interface, but for output rather than input.
It's no big deal to add a remapper although I'd do the renaming on the final xml tree. After all, with a proper css any xml file should render ok and I'd rather stick to generic tagging.
The html files do render in a browser but the epub files can’t be read on a ereader what makes the function useless for me. Changing the tags from “paragraph” to “p”, adding body tags and using a different namespace declaration let me produce a usable file but should this really be necessary?
the alternative is to use html tags and of course there is a limited set which in turn means all kind of 'class' attributes and additional css which might as well not be supported by an ereader device .. the same is true for math ... not supported by most ereaders so one ends up with fake math via css which looks horrible etc etc
I would really prefer to use only html tags when a epub file is produced, now the files can be only viewed without problems in firefox (with the epubreader extension) which is nonsense. With the epub 3 standard also mathml is supported and when a reader is used which doesn’t understand it that’s no problem because the standard is AFAIK backward compatible and unknown functions are just ignored. Wolfgang