Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Extended TeX: past, present, and future-> 1

Submitted by Hamburg
Hamburg (2890317) 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 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 in regard to solutions of important problems in typesetting."

Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Extended TeX: past, present, and future

Comments Filter:
  • It is great to see the author list the pros & cons of TeX. Interesting that after 20 years of font & layout that typography's hard problems are still hard.

    Issue 3.4 Page layout "Baseline to Basline" spacing (leading) is one reason I hate many [programming] fonts. You are forced to accept whatever "default" value the font designer uses. While fonts such as Proggy, Consolas, are good (without that stupid anti-aliasing blur) they don't go far enough by having too big a value of leading. I've design

Have you ever noticed that the people who are always trying to tell you `there's a time for work and a time for play' never find the time for play?