Quote:
Originally Posted by frabjous
1) For the fourth time, LaTeX does not need to use a DVI driver, and even if it did, 2) It support for differ font sizes and different page sizes/styles, and putting in commands that are only activated when certain font or page sizes works whether it's using the DVI driver or a PDF driver. On what basis do you say it's support is broken? It works flawlessly when I've done it, and yes, I've done it. In fact, I'll demonstrate in just a moment.
|
No, you don't
need to use a DVI driver, but any other means of rendering is going to have higher overheads. It's what DVI is designed for, after all. In the meantime, you're saying that the PDF output works? Well yea, but that dosn't deal with my requirement, for instance, for multiple screen sizes without using different documents and losing my annotations.
(Also, as far as I know, there isn't a suitable DVI driver for the ARM architecture so one would have to be written)
Quote:
|
(Probably with CSS tricks it could be emulated, but it would be a lot of work.)
|
Actually, while MathML isn't embedded into readers at present, it can be used in ePuB documents as an island, along with backup images, and in future renderers which support it, they'll render. You can even include a SVG and render that on platforms which support it as well.
And the next version of ePuB is very, very likely to mandate MathML (and there's no reason it can't be added in firmware, it's not a complex or large package).
And honestly, do you disagree that MathML is ideal for what you're trying to do? ePuB is a new format. It'll get there, and rapidly. I think your problem is more with the current version of ADE, which I'm not defending, and publisher lazyness* rather than ePuB.
(*I'm told darknet books often have better formatting than official ones)
(I'd note that modern TeX editors can convert to MathML, it's not like it's restricted to HTML-derived formats)