David A Roberts

@dginev what needs to be added to pandoc's abstract model to support LaTeXML?

@dginev It would be really cool to have a "universal" document model, but as you say, it's a tricky problem. I've spent a little bit of time thinking about it...

Definitely, I'm very much in favour of native apps on IPFS, for both code and data distribution. See my comments on ipfs/ipfs#4 and jbenet/random-ideas#27 for example. Adding an executable bit...

Yes, @bramstein it would be fantastic to have your input on this :) --- @rht Yeah, I saw that issue, and was somewhat amused by this comment: > [...] is...

> I think the performance argument is not a very good one. Me either > The bigger issue is that some parts of CSS are incompatible with the TeX model....

Alright, here's my first approximation (just using greedy justification for now): - [Before](http://www.albany.edu/~hammond/demos/Html5/arXiv/LaTeXML/1104.2804/mkc0606.html) - [**After**](https://ipfs.io/ipfs/QmWGmrkcFTDRCEzdPg2HjKxLaY8YrRR9JBoVps5aeNptzM/LaTeXML/1104.2804/mkc0606.html) - [PDF](http://arxiv.org/pdf/1104.2804v3.pdf) for comparison

@rht most of that 4MB is poorly compressed images, which can be improved (eg. using SVG instead of PNG) Re pagination: I don't think trying to emulate physical books too...

Another example: https://ipfs.io/ipfs/Qmav57P5mmwcpUtmgRb2tp9j6YpXZdgobxDv7VBeJtgtCp/

@rht yes, section/paragraph linking is definitely something I'd like to do > For the qualia of a book, now that it is confined to a flat screen, it has less...

I've broken this into a separate project now: https://davidar.io/TeX.js/ Please submit bugs / feature requests to https://github.com/davidar/TeX.js/issues