Slashdot Mirror


Extended TeX: Past, Present, and Future

First time accepted submitter Hamburg writes "Frank Mittelbach, member of the LaTeX Project and LaTeX3 developer, reviews significant issues of TeX raised already 20 years ago. Today he evaluates which issues are solved, and which still remain open and why. Examples of issues are managing consecutive hyphens, rivers of vertical spaces and identical words across lines, grid-based design, weighed hyphenation points, and overcoming the the mouth/stomach separation. Modern engines such as pdfTeX, XeTeX and LuaTeX are considered with regard to solutions of important problems in typesetting." Note: When TeX was first released, Jimmy Carter was president.

7 of 300 comments (clear)

  1. TeX for Math by rrhal · · Score: 5, Interesting

    When TeX was new people were not accustomed to seeing well type set documents unless they came from a legitimate publisher. I wrote several college papers in TeX and I think the presentation let me get a few mistakes past my teachers. I've not seen anything better for formulas - even today TeX documents have a more polished feel to them.

    --
    All generalizations are false, including this one. Mark Twain
    1. Re:TeX for Math by K.+S.+Kyosuke · · Score: 5, Informative

      There's always TeXLive.js, if you actually need full (La)TeX environment in your browser.

      --
      Ezekiel 23:20
    2. Re:TeX for Math by jd · · Score: 5, Interesting

      Well, with WebKit up the proverbial creek these days, a new rendering engine would make sense.

      The question would be whether you could create a TeX-alike engine that supports the additional functions required in HTML and can convert any well-formed SGML document into a TeX-alike document. If you could, you can have one rendering engine and subsume HTML and XML entirely within it.

      The benefits of doing this? The big drawback of style sheets is that no two browsers agree on units. TeX has very well-defined units that are already widely used. These also happen to be the units industry likes using. Eliminating browser-specific style sheets would be an incredible benefit.

      The big drawback of the Semantic Web is that everyone, their brother, cat and goldfish have designed their own ontologies, none of which interoperate and few of which are any good for searching with SPARQL. LaTeX has a good collection of very standard, very clean methods for binding information together. Because it's standard, you can have a pre-existing ontology libraries which can be auto-populated. And because LaTeX is mostly maintained by uber-minds, rather than Facebook interns during their coffee break, those ontologies are likely to be very, very good. Also, microformats will DIE!!!! BWAHAHAHAHAHAHAHAHA!

      The big drawback with HTML 5 is that the W3C can't even decide if the standard is fixed, rolling or a pink pony. TeX is a very solid standard that actually exists.

      Ok, what's the downside of TeX? There's no real namespace support, so conflicts between libraries are commonplace. I'm also not keen on having a mixture of tag logic, where some tags have content embedded and others have the content enclosed with an end tag. It's messy. Cleanliness is next to Linuxliness.

      Parsing client-side is a mild irritant, but let's face it. AJAX is also parsing client-side, as is Flash, as are cascading style sheets, etc, etc. The client is already doing a lot (one reason nobody has a fast browser any more), so changing from one set of massive overheads to another really wouldn't be that much of a pain.

      Ok, so if we consider TeX the underlying system, do we need a TeX tag? No. We would rather assume all parts of a document not enclosed by an SGML tag are TeX. This would be a transitory state, since you could then write SGML-to-TeX modules for Apache, IIS and other popularish web servers. The world would then become wholly TeXified, as it should be.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:TeX for Math by gweihir · · Score: 5, Interesting

      Indeed. We just decided to move to LaTeX again for all documents that customers do not have the right to edit (most of them). The alternative was Word 2010.

      Reasons are far better look, far better to edit, no distractions while edition (MS GUIs suck), can be edited on any OS, .eps capability, svn compatible, easy separation of documents into separate files, etc. Took me 3 days of LaTeX hacking to make the style file and templates match the Word Template, but well worth it, as now it is done and will not surprise us all the time like the toy-level MS Word does.

      For stuff that customers do edit, we are stuck with MS trash, unfortunately. But even there we are thinking of writing it in LaTeX first and then move it over with latex2rtf for the final version. Far more efficient.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    4. Re:TeX for Math by Anonymous Coward · · Score: 5, Insightful

      The question would be whether you could create a TeX-alike engine that supports the additional functions required in HTML and can convert any well-formed SGML document into a TeX-alike document. If you could, you can have one rendering engine and subsume HTML and XML entirely within it.

      TeX is a document typesetting language. HTML, regardless of its flavor, is a markup language that describes the document's contents but doesn't tell the browser how to lay it out.

      There's no hope for TeX-as-HTML ever working because they're built on fundamentally incompatible document models.

      -JS

      P.S. If you want to see what math for HTML looks like, go look at MathML. Next, try actually writing a non-trivial equation in MathML, something like

      $\int_{-\infty}^{\infty} e^{-x^2} dx = \sqrt{\pi}$

      Then you'll understand why those of use who do this for a living still write our papers in TeX. Even if you don't know TeX, you can probably guess what my equation should look like; you wouldn't say that about the MathML.

  2. Re:Jimmy Carter was president of TeX?! by fyngyrz · · Score: 5, Funny

    Yes, but there was that helicopter crash; the typesetting community always blamed TeX for that, and ever since then, TeX has been relegated to doing font work in the third world, charity undertakings and the like. And really, who wanted to be limited to 55 fonts per document? Some of us type in the fast lane, buddy.

    --
    I've fallen off your lawn, and I can't get up.
  3. so old it must be replaced... by smoothnorman · · Score: 5, Funny

    nothing that old can possibly be relevant anymore (cf "trust no one over 30"). it should be replaced with something more responsive to a one-hand touch interface abbrev friendly imho. math, a central theme in TeX, no longer has any relevance to the modern world (just ask any millionaire agile scrum extreme php programmer). any remaining bits of math are done entirely by app; the vestigial remnants of the usefulness of "math" can only be found in the interjections of animated characters. only a tiny ancient dying breed of tenured academics (and i suspect *europeans*) would ever seek typography beyond the standards of MSWord. page layout was forever perfected by expensive per seat layout software around 1996 and requires no more changes. markup languages are too hard to learn. anything that requires a compiling phase has gone the way of C++. the world is better now as everything old and outmoded quickly recedes. sine-die.