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.

49 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 ModernGeek · · Score: 3, Interesting

      HTML 5.1 needs a TeX tag... I'd do anything to see it. What's stopping it from happening? Someone should fork WebKit and do it.

      --
      Sig: I stole this sig.
    2. Re:TeX for Math by fuzzyfuzzyfungus · · Score: 3, Interesting

      Presumably imply the existence of a feature-complete TeX implementation in the browser, that would render and display whatever TeX snippet was included within the tag...

      I'm pretty sure that there are some server-side convenience plugins for at least a few of the major OSS CMS packages that will let you use TeX or LaTeX and then digest the results into images that get plunked into the actual HTML that gets shoveled out to clients; but the odds of coaxing browser makers to include a completely separate, extremely powerful, and highly mature(if baroque) rendering engine alongside the one they already have, just to support a TeX tag seem slim...

    3. Re:TeX for Math by PopeRatzo · · Score: 3, Insightful

      Way back when my wife was getting her PhD math, I had to learn Tex to help her. She let me bounce my head against Tex while she was busy with her fluid dynamics and then I'd get to explain it to her. I could never understand how there are mathematicians who can easily write in Tex the way I'd write in a word processor. It all just seemed so opaque. De-bugging errors was among the most frustrating things I've ever done on a computer. But the results are impeccable. I still don't think there is a better program for typesetting equations. Or I should say, I don't know of a better one. But if there is one, can someone kindly tell me?

      --
      You are welcome on my lawn.
    4. 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
    5. Re:TeX for Math by jd · · Score: 3, Insightful

      Whereas now, people are still not accustomed to seeing correctly typeset documents and are now completely used to vast numbers of typos, malformed web pages, poor indexing via the semantic web, gratuitous XML, excessively long style sheets, browser incompatibilities, Javascript...

      --
      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)
    6. Re:TeX for Math by semi-extrinsic · · Score: 4, Informative

      Modern LaTeX is quite a bit better at giving good error messages, unless you try to do very complex things. Combining lots of packages for heavy customization is the prime example; I once spent half a day setting up custom chapter titles with a side-by-side miniature table-of-contents and epigraph below a title where the chapter number extruded into the margin, and drop caps at the start of the first paragraph. But the end result was beautiful.

      --
      for i in `facebook friends "=bday" 2>/dev/null | cut -d " " -f 3-`; do facebook wallpost $i "Happy birthday!"; done
    7. 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)
    8. 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.
    9. Re:TeX for Math by Daniel+Dvorkin · · Score: 3, Insightful

      I could never understand how there are mathematicians who can easily write in Tex the way I'd write in a word processor.

      I can't really explain it other than to say "you get used to it." After a while, the markup becomes transparent; if you're typesetting an equation, for example, you see the layout in your head while you're typing the markup. Which makes it much easier than using an equation editor in a word processor, really--compounded by the fact that equation editors are universally awful.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    10. Re:TeX for Math by gtall · · Score: 4, Informative

      I just gave a talk for management. One fellow remarked on the quality of my slides and didn't think they were done using PP. Yep, I said, they are Latex (Beamer), and I can cut and paste from my papers. Using PP for math will make you go blind.

    11. Re:TeX for Math by michael_cain · · Score: 4, Insightful

      ...no distractions while edition (MS GUIs suck)...

      At some point there was an internal study at Bell Labs after WYSIWYG word processors were beginning to be available that found most people spent 20% of their time futzing with how the document looked instead of writing. Most of that time was wasted because subsequent changes were going to wipe out whatever the little tweaks had been intended to accomplish.

      Interesting that today you can buy programs whose primary purpose is to blank all of your display except for a green-on-black mono-spaced text window. Sold as an aid for professional writers who need to pound out umpteen pages of text per day, so need to avoid interruptions and distractions while composing.

    12. Re:TeX for Math by Anonymous Coward · · Score: 2, Interesting

      "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."

      Put TeX into HTML and that moderately true statement will quickly become absolutely false.

      Stack Overflow has been keeping many of the degenerates away from Usenet. I really don't want to go through the same decade-long cycle of idiocy in TeX-land.

      Anyhow, TeX is just too difficult. There's something about a virtual machine based on recursive macros which can drive any uber-hacker to tears. There's no hope for the HTML crowd. You may as well shoot them all in the knee caps, send them home, and tell them to thank you.

    13. 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.

    14. Re:TeX for Math by frisket · · Score: 2

      At some point there was an internal study at Bell Labs after WYSIWYG word processors were beginning to be available that found most people spent 20% of their time futzing with how the document looked instead of writing.

      Do you have chapter and verse on that? Figures quoted at the XML-in-Practice conference in Boston in 2007 put it at 30-60% and a new study claimed to have seen 75-90%. I have raised this on a related mailing list but have been unable to identify the source as the organisation who ran the conference has erased all trace of it from their web site.

      Most of that time was wasted because subsequent changes were going to wipe out whatever the little tweaks had been intended to accomplish.

      I keep tellin' 'em but they never listen.

    15. Re:TeX for Math by sFurbo · · Score: 4, Informative

      When all your writing is text, the whole point of Tex is lost, and you might as well use word.

      No it isn't. Apart from the ease of writing equations, one major point for LaTeX is that you can just write the damn text and you don't have to worry about how it looks. The final result is going to be beautiful. In Word, you can choose the font and size of all levels of headings, the line spacing and the margins, and even when you have spent time doing that, it still doesn't look as good as LaTeX does out of the box.

    16. Re:TeX for Math by jgrahn · · Score: 3, Informative

      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 [...] svn compatible, [...]

      That's a rather laconic way of putting it. Real revision control gives you a whole array of essential things, like collaborative editing, an audit trail, the ability to work on version 2 while version 1 is still being finalized ... That's why *all* binary document formats (not just MS Office) fail my personal test.

    17. Re:TeX for Math by TheRaven64 · · Score: 2

      Using PP for math will make you go blind

      I've switched to Beamer for my presentations, but for OS X there was a nice system service that sent the selected text through pdflatex and returned the resulting PDF. It also did some tricks to embed the TeX source in the PDF, so there was an inverse operation. That made formulae in Keynote presentations easy: just type the TeX version, hit a keyboard shortcut, and you get it replaced by the PDF. Hit another shortcut and you can edit it again.

      --
      I am TheRaven on Soylent News
  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. Wrong Font For Program Name by Freshly+Exhumed · · Score: 4, Funny

    Oh dear oh dear, I hope Donald Knuth doesn't see that Slashdot doesn't seem to allow the correct METAFONT for displaying the program name! Pissing off Donald Knuth would be like kicking the Dalai Lama.

    Is it possible to represent it in it's proper format via this version of Slashcode?

    --
    I deny that I have not avoided attaining the opposite of that which I do not want.
    1. Re:Wrong Font For Program Name by Anonymous Coward · · Score: 2, Insightful

      What a strange thing to ask of a website that refuses to allow non-ASCII characters in 2013.

    2. Re:Wrong Font For Program Name by mark-t · · Score: 3, Informative

      Knuth doesn't seem to be too bothered by the fact that his program is rendered in standard ascii characters as 'TeX', rather than how the name is typeset in his books, since his very own home page seems to do likewise.

    3. Re:Wrong Font For Program Name by K.+S.+Kyosuke · · Score: 2

      Well, it was decided early on that there are many Perl people who might want to post Perl snippets in comments, so the inclusion of these characters was a no-brainer. Also observe how the APL people got snubbed. I blame it on the Perl folks' jealousy.

      --
      Ezekiel 23:20
    4. Re:Wrong Font For Program Name by martin-boundary · · Score: 3, Funny

      True, but he uses a special Tektronix terminal with a custom ROM that computes on the fly the optimal TeX rendering of any HTML document while he's browsing it. Please nobody tell him what the rest of us see...

  4. Old tech, and limited by Okian+Warrior · · Score: 3, Interesting

    I just recently reviewed the landscape of document writing systems for a client.

    TeX (and LaTeX, and such) are a fine choice for specific purposes. There's a lot of functionality, it's robust and widely used. If you're writing a journal submission paper, it's a good choice.

    The publishing landscape has changed. There are now many more types of document (help files, web pages, books, articles, owner's manuals, laws, contracts) that people want to write, and the TeX family is inconvenient for many of them.

    XML is a more comprehensive document content specification. It easily covers all of the common document types (including those for which the TeX family is useful) and is extensible in a straightforward manner.

    As a specific example, DocBook (a specific XML scheme) covers all cases where TeX is useful, and many more. An XML processing system can convert to any presentation format (HTML, XHTML, PDF, Microsoft Help, Text), and it's straightforward to build converters for new formats.

    (There are also other XML schemas.)

    The drawback of DocBook and XML in general is that installation is a nightmare. So far, there's no "one package install" that gets the author up and running. XML processing is a series of steps, with each step served by one of several open source packages. The author must choose and install software for each step, usually without any indication which is best for his purposes. This only needs to be done once, though. (For open source - paid software packages have this sorted out.)

    (For example, see how long it takes you to install DocBook 5.x on a windows system.)

    The TeX family is a good choice, but if you're not already using it consider learning a more recent solution.

    1. Re:Old tech, and limited by retchdog · · Score: 4, Insightful

      structure is one thing, output is another. show me some docbook-rendered math that doesn't suck.

      --
      "They were pure niggers." – Noam Chomsky
    2. Re:Old tech, and limited by colinrichardday · · Score: 2

      There are now many more [wikipedia.org] types of document (help files, web pages, books, articles, owner's manuals, laws, contracts) that people want to write, and the TeX family is inconvenient for many of them.

      I'll grant you that (La)TeX makes for lousy web pages, but books and articles? Is XML that much better for contracts and owner's manuals?

    3. Re:Old tech, and limited by jd · · Score: 3, Informative

      Never had any problem writing books in LaTeX. The main difficulty has been in deciding whether I want a modern or medieval structure.

      Docbook, on the other hand, I hated. I helped with the writing of a few chapters of the Linux Advanced Traffic Control book, which was abandoned in part because Docbook was such a disgusting system.

      XML is useless for typesetting. It's not really that useful for organizing anything - you'll have used XML-driven databases, but you'll have never used an XML-driven database that had any performance or serious functionality. (LaTeX doesn't do databases, either, but it doesn't pretend to. It has external engines for databases, which are actually quite nice.)

      Web pages? Never had any problem embedding HTML in LaTeX. In fact, I have very very rarely found ANY document style to be LaTeX-incompatible. Load up the correct document type, load up the appropriate stylesheets and you're good. Yes, spiral text is hard. Yes, embedding HDR images can be a pain. Yes, alpha blending isn't that hot. But how often do you use any of these for owner's manuals or contracts?

      There are more table classes than I'd really like, and some of the style coding is scruffy, but I challenge anyone to find a genuine, common document type that LaTeX* cannot do as well as or better than any non-TeX wordprocessor, DTP solution or XML-based system. (Non-TeX means you can't compare TeX with Scientific Word, TeXmacs or any other engine that uses TeX behind the scenes.)

      (To make it absolutely clear, "as well as or better than" can refer to any one or more parameters. So if I get better-quality output, that's better than. If I can achieve comparable results with cleaner, easier-to-maintain syntax, that's also better than. To win, your solution has to not merely equal but actually exceed what I can do on EVERY parameter, or you have failed to demonstrate something that supercedes.)

      A bitcoin to anyone who can do this.

      *I am including all dialects of LaTeX here, so LuaLaTeX, PDFTeX, etc, are all things I can consider on my side, as are all WYSIWYG and WYSIWYM editors, Metapost, supplemental services, style sheets, etc. Since this is versus a specific alternative, anything comparable for that specific alternative is fair game for you to use, but you can't mix in other alternatives. It has to be one versus the complete TeX family if you want to prove your point.

      --
      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)
    4. Re:Old tech, and limited by jd · · Score: 3

      TeX has control elements for describing structure, since structure is a key part of typesetting. Since these elements are macros, they're programmable, although not truly abstract as in XML. About the only thing I can think of that XML can do for document structure that TeX cannot is out-of-order elements, and I'd argue that out-of-order is incompatible with structure.

      In database terminology, XML is a key-data pair system. The data can be anywhere in the XML file and you need some sort of key to know where it is and/or when you've found it. (Since XML is not organized, you can't do random access to get at the key. You have to load it in and organize it, in which case it isn't XML, or you have to sequentially search it.)

      TeX is a semi-sequential structure, with relationship links between specialized data tables. Again in database terms, it's a set of batch sequential files with crude but useful support for concrete data association. Because it's batch sequential, real-time usage gets hairy. Big deal. Those in the middle of writing should be concerned with the writing. It would be nice if editors had better error-detection, but it's not usually that critical.

      --
      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)
    5. Re:Old tech, and limited by colinrichardday · · Score: 2

      And how do you put math in HTML? And if you don't have math converting from LaTeX to HTML isn't that hard.

  5. 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.

  6. What about pictures? by TechyImmigrant · · Score: 4, Insightful

    TFA doesn't address the extreme crapitude of embedding pictures in Tex. I could drive myself to drink converting everything to EPS, or poorly scalable bitmaps before embedding them, but I don't want to.

    The issues of imperfect typesetting are not the barrier to entry for potential TeX users. Picture embedding is.

    --
    I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    1. Re:What about pictures? by Hamburg · · Score: 2

      Embedding of PDF images is supported, so scalable. And most formats can be converted to PDF, there are even easy-to-use PDF file printer if a program doesn't directly support it. No need to convert to a bitmap format. Bitmaps are supported, but I would use that only if the image is already a bitmap. And you can embed it floating, for automatically optimized page breaking.

    2. Re:What about pictures? by retchdog · · Score: 2

      pdflatex can accept basically anything other than EPS. yeah, including graphics is still a major pain, but converting to EPS is not typically a problem.

      --
      "They were pure niggers." – Noam Chomsky
    3. Re:What about pictures? by jd · · Score: 2

      Think it's graphicsx. One of the packages, anyways, lets you include PNGs, JPGs, etc. No problem. I include graphics all the time with LaTeX, very few of which are EPS. True, graphics import isn't as clean as I'd like (it's a bugger to remember all the different nuances of each type of graphics format you can use and through which package you need to use it with).

      I also don't like the fact that vector images require you to master Asymptote, Metapost and an armful of other systems. This can - and should - be massively cleaned up.

      So, whilst I agree that TeX has crappy image handling, it's not nearly as bad as you depict.

      --
      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)
    4. Re:What about pictures? by aisaac · · Score: 2

      Think it's graphicsx. One of the packages, anyways, lets you include PNGs, JPGs, etc. ... I also don't like the fact that vector images require you to master Asymptote, Metapost and an armful of other systems. ... So, whilst I agree that TeX has crappy image handling, it's not nearly as bad as you depict.

      It is also not nearly as bad as you depict. Vector drawing is handled nicely by pgf/tik. If you want meta-control of tikz, you can use the wonderful tikz backend for matplotlib. There are also beautiful ways to produce EPS or (better yet imho) PDF for LaTeX, with embedded TeX fonts, including Matplotlib and the amazingly powerful PyX. Btw, the graphics inclusion package is graphicx.

    5. Re:What about pictures? by frisket · · Score: 2

      Does Visio not provide PDF export of images? Sounds like a crap system to me if it doesn't.

    6. Re:What about pictures? by archshade · · Score: 3, Informative

      I know you are trying to be funny, but searching for ``latex images'' on google the first page is all tutorials on how to insert an image into a Latex document. The third link was a link to a google image search wich did have the kind of thing you are implying. still 9/10 relevant results is not bad.

      --
      Most Damage is done by people who are AWAKE
  7. Re:TeX for Otherstuff by xclr8r · · Score: 4, Informative

    Couple of good reads regarding LaTeX. 50 Shades of LaTeX: The Pain the Pleasure http://airminded.org/2005/11/18/latex-the-pain-the-pleasure/ http://crookedtimber.org/2005/04/27/fetishizing-the-text/

    --
    Beware of those who profit off the docile and persecute the unbelievers.
  8. The biggest issue is old, dead modules by Anonymous Coward · · Score: 2, Informative

    If you're trying to learn LaTeX, the biggest barrier is that you'll do a search and find tutorials that recommend using old, broken modules. Then you'll change something and wonder "WTF does LaTeX not ever work?!"

    It's a great idea, if LaTeX is behaving mysteriously, to use nag and l2tabu, and especially ChkLatex to flag typos and mistakes \macro word. (The macro will eat the whitespace before word, either \macro{} word or \macro\ word is what you meant.) It's also best to stick with only packages in TeXLive.

    But always, always before you use a package, find it on CTAN and make sure you've got the latest and greatest, and check the docs that there's not some disclaimer like, "by the way, this package is only here for compatibility, please use package X."

  9. Re:What in the world is "mouth/stomach separation" by asshole+felcher · · Score: 2, Informative

    It's sort of like C where you have a preprocessor ("mouth") which does macro expansion and text replacement and then the actual compiler ("stomach").

    Quoting this paper:

    The usable programming language has to consist of both parts [mouth and stomach] because the assignment capabilities of the stomach are needed in order to define macro definitions and to read or write text, i.e., to produce an output. The mouth is necessary for all tasks that needs an iterative application or a recombination of input tokens. TEXâ(TM)s stomach uses the macro processor for almost all commands to scan the command arguments. Additionally, while scanning the arguments of many stomach commands, such as \write, \edef, count or dimension register assignments, all tokens are expanded. Thus stomach operations are not allowed in these places, leading to the problem of fragile commands in moving arguments. This is partly taken care of with LATEXâ(TM)s \protect.

  10. Re:The last command-line word processor by PhamNguyen · · Score: 3, Interesting

    I agree, the need to compile is a big time sink. Hunting for a missing brace or dollar is just horrible. I and many people I know (all long time users of LaTeX) switched to using LyX and only exporting to LaTeX for the final formatting (e.g. using a journal's style guide). Unfortunately there is no quick fix for LaTeX: the power of the language means that gui's like LyX can only deal with a subset of the language, and yet this power is necessary in order to allow for all the packages that LaTeX supports (and especially to support existing packages).

  11. Document archiving. by Robert+Frazier · · Score: 2

    I use LaTeX for almost everything from articles to memos, and have been doing so since the late 1980s. Last year I needed to print part of my dissertation, which is from 1990. With my current system, using a modern version of LaTeX, but including the special macros I used for the dissertation, it formatted the same in 2012 as it did in 1990. Try that with MSWord. :)

    In addition, having text files with macros certainly makes storage/searching/organizing much easier. The files compress well, and searches, etc., can be done using standard tools such as grep.

    Best wishes,
    Bob

  12. mixed feelings by ssam · · Score: 4, Insightful

    while i have written a thesis in latex, and could not imagine using anything else for papers, i still get frustrated by it.
    * any problem is solvable with enough searching online, but the solutions are often like magic. for example i often have figure filenames like "x2.3_y3.4.pdf" latex gives a weird message, search around and eventually you find a forum thread that tells you to put some extra arguments in the includegraphics call, or if you are lucky you might find a mention of the grffile package. in all the years of using it I have never built up an intuition for solving these issue (by comparison programming and linux pretty much make sense to me).
    * multiple ways of doing things. should i use \begin{center} or {\centering text text tex}. probably they both work fine, but each of them breaks something else in some obscure case.
    * why are some things \command{text text text}, some {\command text text text} and some \begin{command}. compare with XML/SGML where everything is achieved with nesting tags.
    * can the output be cleaned up? when i run pdflatex i get several screen-fulls of messages. really it should be showing me errors and optionally warnings.
    * the interactive mode when it hits an error. i am sure there is nothing productive i can do in that shell. why is it so hard to get out of. why is -halt-on-error not default?
    * why do i have to run pdflatex twice? why can't it figure out if a reference has changed? latexmk (or a good makefile) helps, but it took me years to find it.

    1. Re:mixed feelings by crazyvas · · Score: 2

      Well summarized list! I've used LaTeX for years as well, and could immediately relate.

      tex.stackexchange.com is helpful (wish it existed years earlier), and will hopefully become much more helpful. For instance: http://tex.stackexchange.com/questions/23650/when-should-we-use-begincenter-instead-of-centering

      But I completely hear you: it's frustrating I have to constantly look up things on a forum (or ask the local TeX guru) even after years of advanced usage. BTW, I use https://code.google.com/p/latex-makefile/

  13. Re:The last command-line word processor by dfghjk · · Score: 3, Informative

    "TeX still had a compile-run-debug workflow, and without a graphic display, you had to run a hard copy on something like an electrostatic printer or a daisy wheel printer to check the results."

    When TeX was new, "a graphic display" was common and there were many previewers available pre-1.0. The idea that anyone previewed work on a daisy wheel printer is absolutely ludicrous. Never happened and would be useless.

    "Then you could go to the phototypesetting machine."

    No, you would go to screen previewer, then a laser printer, and then only to a phototypesetter if you were publishing. You sound like someone who didn't use TeX in those days.

    "Once everybody got an interactive display good enough to view the output of TeX..."

    You mean like a PC in 1985? Seriously, you pretend to be a historian but you aren't one. I, on the other hand, cowrote one of the first PC TeX previewers, in...1985. I am actually familiar with how these tools were used then, and it's clear you weren't a TeX user. As an Interleaf user, it seems you were the type privileged by limitless company money. Not many even had access to a machine capable of running Interleaf in those days. In my next job I worked with someone who was an Interleaf fan and who had the clout to get the company to buy him, and only him, a seat. He liked it, no one else used it or really even got to see its output, and TeX worked well at zero cost.

    Many consider "compile-run-debug" to be an advantage but perhaps not since it became trendy to call that a "workflow". What-You-See-Is-All-You-Get.

  14. Old timers by michael_cain · · Score: 2

    Fun to see just how many of the people that jump on a discussion like this one have 4- and 5-digit user numbers :^)

  15. Re:TeX Sucks by Hamburg · · Score: 2

    One should understand the tools for his or her work, more or less, depending on the expectation of the result. MS Office was made easier, but I wouldn't expect as good results and there's not as much control over the document. But home and office users often don't need it, so choosing the easier one is ok.

  16. Re:hah by Genda · · Score: 4, Insightful

    Pretty much just incidental. Reagan's interest in "High Tech" was mostly limited to military applications (like Star Wars) which turned out to be huge financial boondoggles. He killed financial support for solar and other alternative energy technologies and put James Watt in charge of the environment (a man who believed we should use up the environment as soon as possible to hasten the second coming.)

    By comparison, Eisenhower set the economic stage for Bell Labs, IBM, Dupont and DOW Chemicals and a brand new government space program named NASA. The JFK expanded all of these things dramatically including the mandate for a man on the moon. Clinton was the seminal power behind America's global advance in internet technologies and in 2000 we were leading the world. With Bush's cutting of support of the internet and redirecting economic focus on fossil fuel, war and housing, America has fallen behind Asia and even Europe. So Ronny may have presided over the 1980s expansion of high tech it would be very hard to claim he was a friend to advancing technology.