21–30 of 68 posts
"Ten years later, in 1978, his work bore fruit"
This gets things pretty wrong. He got the idea in 1977, and his estimate of "this will take 6 months" was pretty close, in that the initial version was finished sometime in 1978. It then took about another ten years to be "actually done". (Rewrite, add features, fix bugs, create Metafont, create WEB, etc...)
It's of course never going to be as good looking as MathJax or something like that -- but it may be more appropriate to be able to treat it as plain Unicode text in some cases.
For instance, it works in title fields across the web and search engines will understand it better than anything else.
Are there any other solutions to document typesetting with latex-like features? TeX is very obtuse for someone who hasn't been using it for a long time.
Just a bit of historical correction. The article/post says: "Ten years later, in 1978, his work bore fruit" This gets things pretty wrong. He got the idea in 1977, and his estimate of "this will take 6 months" was pretty close, in that the initial version was finished sometime in 1978. It then took about another ten years to be "actually done". (Rewrite, add features, fix bugs, create Metafont, create WEB, etc...)
I have found KaTeX to be the best currently-available solution. In particular, it can be rendered without client-side javascript.
Completely besides the point, but that integral evaluates to sqrt(2pi), not sqrt(pi).
(I'm a co-founder at Overleaf.com, which does collaborative 'LaTeX in the browser' in a different sense.) I like the idea of a 'sane' subset of LaTeX that is easy to publish to the web. There are tools like LaTeXML and TeX4ht that try to convert general LaTeX documents to (X)HTML, but it's a very hard problem. Some difficulties arise from the fact that TeX is just very hard to parse in general. Even the first stage o…
(I'm a co-founder at Overleaf.com, which does collaborative 'LaTeX in the browser' in a different sense.) I like the idea of a 'sane' subset of LaTeX that is easy to publish to the web. There are tools like LaTeXML and TeX4ht that try to convert general LaTeX documents to (X)HTML, but it's a very hard problem. Some difficulties arise from the fact that TeX is just very hard to parse in general. Even the first stage o…
That's probably the only approach that really makes sense:
During the past decade I was surprised to learn that the writing of programs for TeX and Metafont proved to be much more difficult than all the other things I had done (like proving theorems or writing books). The creation of good software demand a significiantly higher standard of accuracy than those other things do, and it requires a longer attention span than other intellectual tasks.
(I'm a co-founder at Overleaf.com, which does collaborative 'LaTeX in the browser' in a different sense.) I like the idea of a 'sane' subset of LaTeX that is easy to publish to the web. There are tools like LaTeXML and TeX4ht that try to convert general LaTeX documents to (X)HTML, but it's a very hard problem. Some difficulties arise from the fact that TeX is just very hard to parse in general. Even the first stage o…
Just a bit of historical correction. The article/post says: "Ten years later, in 1978, his work bore fruit" This gets things pretty wrong. He got the idea in 1977, and his estimate of "this will take 6 months" was pretty close, in that the initial version was finished sometime in 1978. It then took about another ten years to be "actually done". (Rewrite, add features, fix bugs, create Metafont, create WEB, etc...)
Thanks very much for the correction!