3 ms·
I think the big problem with rendering LaTeX client side is that everyone uses different style files, fonts, etc. The options are to either include them all on
by smanek 18y ago
I think the big problem with rendering LaTeX client side is that everyone uses different style files, fonts, etc. The options are to either include them all on the page (which would make it difficult for me to upload a LaTeX file, since I'd have to include half a dozen auxiliary resources). It seems like this problem has been solved adequately well by just having a PDF file (which embeds fonts, and doesn't need style files).
Even if browsers could render LaTeX clientside, I still feel like there would be no real advantage to PDF. Since there is no standard way to embed LaTeX markup in HTML, you would just have to link to a .tex file which the browser could display as a separate page, just like it displays a PDF.
I almost feel like XHTML would be a good fit for this problem. We could develop a XML schema for which a simple bijection to LaTeX markup exists. Then, since XHTML supports using multiple namespaces in a single document, we could include any LaTeX markup natively within an XHTML web page (by prefacing LaTeX markup elements with the proper namespace). You would still have to deal with fonts/styles, but I think that's a much easier problem in this sort of a framework.