Quote:
Originally Posted by Hitch
Yes, but to get back to reality, in which eBooks sold via Amazon outsell pretty much everything else and nobody wants to pay a small fortune for an eBook that is unsupported, or worse, for which Amazon will give you a KQN (Kindle Quality Notice), the reality is, you can't "only" use MathML. You can't "only" use SVG.
You either use MathML+JPGs or SVG+JPGS. Them's the choices. And that's a whole other thang.
BTW, our experience with Pandoc "spitting out" MathML from LaTEX--yeah, maybe that works for you, on YOUR own work. We get files that are ancient, or using a version of LaTEX from when Fred & Barney were riding Brontosauruses to work and the cruft we get out is fugly. Just saying.
I have yet to see one single laTEX conversion--ever--from some typical walk-in-the-door guy's files that wasn't a goddamned nightmare. It's all well and good if the person using it, is the person who will be making the final file. However, I seem to have a magic ability to attract half-baked college professors that suddenly find themselves without their latest TA or PA or whatever and only know how to do things ONE way and it's invariably the bloody WRONG way.
/rant.
(Sorry, listen, I'm all for someone, some genius, somewhere, coming up with a supported way to do MathML. I really am. But in the meantime...)
Hitch
|
You wouldn't pay a plumber to turn off the tap would you? You're mainly going to see the non-trivial cases.
I get why MathML is not typically used, but I also never see MathML+JPGs. Too many of my books are just images. I get people want to support whatever Amazon is doing or that Sony reader from 2008 to squeeze out that extra sale but ideally ePub stores and creators would provide multiple options, a MathML version where it works, a SVG version and a crusty PNG version. Instead I get one version that is 10x larger and slower to use than a comparable PDF even though my device supports the latest features.