3 ms·
> after successfully completing the task ZERO times There's a Knuth quote about how the aim of TeX was to allow anyone to create properly typeset documents. I
by nailer 8y ago
> after successfully completing the task ZERO times
There's a Knuth quote about how the aim of TeX was to allow anyone to create properly typeset documents. I can't find the exact source, but https://www.tug.org/whatis.html https://www.tug.org/whatis.html should give you some idea.
This individual wasn't able to. Last time I looked at TeX it (or metafont specifically) often seemed to default to bitmap fonts. That's a poor default - a bug by today's standards - but Knuth has a different definition of 'bug' than you and I do. Maybe you should spend less time judging users and more time working on improving the software you're advocating for?
- zaarn 8y agoMetafont does produce bitmap fonts yes. However, it's quite good at generating these for arbitrary resolutions, so I don't think this is actually a problem. Though actually using a non-bitmap solution might work better nowadays since the computing power is available now, it's probably good enough as it is.
- wbl 8y agoAnd OT1 works for a long time together with pdflatex. What is it about TeX that makes people think they can ignore the past 20 years of development.
- singhrac 8y agoI think you should spend more time updating your knowledge of TeX :) All jabs aside metafont is separate from TeX in most regards, other than that Computer Modern was made using metafont (but is now widely distributed in a vector format).
- nailer 8y agoYou're missing the point. That metafont is seperate from TeX is irrelevant: the only time someone has to use metafont is with TeX, so metafont is considered part of Tex. PostScript is its own can of worms. People who need typeset documents shouldn't have to concern themselves with it. It's not 1994 anymore, alt.sysadmin.recovery is dead, nobody knows what a 'cluestick' is or what code ID-10-T is, and people generally have stopped blaming users for poor software - which TeX, by Knuth's own standards is.
- fusiongyro 8y agoThis complaint is basically the reason XeTeX was written, which accesses your standard system fonts instead. LuaTeX also handles TTF and OpenFont without trouble. These both produce PDFs instead of DVI or Postscript output (per your comment below).
- nailer 8y agoI'm not sure why you're not replying to that comment, but yes, there's a bunch of software created to have better defaults than vanilla TeX. This reinforces the point.
- icebraining 8y agoNot really, because when people say "use LaTeX", they don't really mean you should use only the original version of the software, they're talking about the overall suite of TeX derived programs.
- nailer 8y agoReally, because workarounds prove the point. Actual TeX doesn't do what people want.
- icebraining 8y agoEven the article says there's a LaTeX fetish. Nobody is pushing vanilla TeX, the point is arguing against a strawman.
- bdamm 8y agoEvolution through composition is not a bug.
- svat 8y ago> There's a Knuth quote about how the aim of TeX was to allow anyone to create properly typeset documents. (Emphasis added by me) I have probably read every single word Knuth published on the topic of TeX, and what you said seems very different from what I've gathered of Knuth's philosophy and style. Knuth intended TeX to be used by someone who cares about typesetting, and the program comes with a nearly 500-page manual (The TeXbook) that was very much intended to be read. In fact, he expected anyone who was preparing any special sort of book (a multilingual bible, or dictionary, or whatever) to change the program itself, and has expressed surprise at people using elaborate macro packages like LaTeX or doing everything in TeX macros. (BTW the page you linked at https://www.tug.org/whatis.html https://www.tug.org/whatis.html is also pretty good and note that it says a lot about typography and the finer details of typesetting, and less about ease-of-use: search the page for "support" and "TeX is not the tool for you".) > often seemed to default to bitmap fonts Actually, TeX uses only font metrics, and the output of TeX is merely a set of instructions about where to place what characters from what font. (A compact binary encoding thereof, in the form of a DVI file.) A separate program is needed for actually using the font and rendering the output. (These days everyone uses pdfTeX or some other program that combines the two and uses vector fonts, but that's the original design.) In any case, for the original task that TeX was designed for (completely specifying the appearance of a book, in a future-proof way however technology may change), it is absolutely crucial to combine it with a program for bitmap fonts (and that's Metafont -- it produces only bitmap fonts). Think about it: the rasterization (converting to bitmaps) has to happen somewhere: if you leave it up to some other technology (the one used by the printer or whatever), then you're back to the same problem that led to the creation of TeX, where in a few decades fonts may be produced by some completely different method and you may no longer be able to produce a book whose appearance is identical (except for the typos you fixed or minor rewrites or whatever) to the earlier one.
- nailer 8y agoI'm aware rasterization has to happen at some point - the issue with metafont is the input, rather than the output. Requiring someone to read a 500 page document to produce a typeset work does indeed indicate a conflict - I would spend some time finding a URL for the Knuth quote but HN really doesn't like people discussing TeX or Knuth in a negative way, and this hasn't been a very productive conversation so far.