diff options
Diffstat (limited to 'doc')
20 files changed, 158 insertions, 4 deletions
diff --git a/doc/context/documents/general/manuals/evenmore.pdf b/doc/context/documents/general/manuals/evenmore.pdf Binary files differindex 300b82c1a..5c4072192 100644 --- a/doc/context/documents/general/manuals/evenmore.pdf +++ b/doc/context/documents/general/manuals/evenmore.pdf diff --git a/doc/context/documents/general/manuals/luametatex.pdf b/doc/context/documents/general/manuals/luametatex.pdf Binary files differindex 07ea65e82..b7784b811 100644 --- a/doc/context/documents/general/manuals/luametatex.pdf +++ b/doc/context/documents/general/manuals/luametatex.pdf diff --git a/doc/context/documents/general/qrcs/setup-cs.pdf b/doc/context/documents/general/qrcs/setup-cs.pdf Binary files differindex ef4afbfb5..f899a9515 100644 --- a/doc/context/documents/general/qrcs/setup-cs.pdf +++ b/doc/context/documents/general/qrcs/setup-cs.pdf diff --git a/doc/context/documents/general/qrcs/setup-de.pdf b/doc/context/documents/general/qrcs/setup-de.pdf Binary files differindex 93f2a87fd..172e9ffb4 100644 --- a/doc/context/documents/general/qrcs/setup-de.pdf +++ b/doc/context/documents/general/qrcs/setup-de.pdf diff --git a/doc/context/documents/general/qrcs/setup-en.pdf b/doc/context/documents/general/qrcs/setup-en.pdf Binary files differindex e8ccc0a93..7a794c838 100644 --- a/doc/context/documents/general/qrcs/setup-en.pdf +++ b/doc/context/documents/general/qrcs/setup-en.pdf diff --git a/doc/context/documents/general/qrcs/setup-fr.pdf b/doc/context/documents/general/qrcs/setup-fr.pdf Binary files differindex 02334dd64..5d50fdee9 100644 --- a/doc/context/documents/general/qrcs/setup-fr.pdf +++ b/doc/context/documents/general/qrcs/setup-fr.pdf diff --git a/doc/context/documents/general/qrcs/setup-it.pdf b/doc/context/documents/general/qrcs/setup-it.pdf Binary files differindex 52852e95b..0fbbf623d 100644 --- a/doc/context/documents/general/qrcs/setup-it.pdf +++ b/doc/context/documents/general/qrcs/setup-it.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-cs.pdf b/doc/context/documents/general/qrcs/setup-mapping-cs.pdf Binary files differindex 2fa97686b..1f3dfefd4 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-cs.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-cs.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-de.pdf b/doc/context/documents/general/qrcs/setup-mapping-de.pdf Binary files differindex cbae3d4b2..dbf9303e3 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-de.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-de.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-en.pdf b/doc/context/documents/general/qrcs/setup-mapping-en.pdf Binary files differindex 044ba7d84..8b3670edb 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-en.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-en.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-fr.pdf b/doc/context/documents/general/qrcs/setup-mapping-fr.pdf Binary files differindex 21eb7f3fd..9782dee35 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-fr.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-fr.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-it.pdf b/doc/context/documents/general/qrcs/setup-mapping-it.pdf Binary files differindex 5ed2b6bb0..7ddfcb598 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-it.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-it.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-nl.pdf b/doc/context/documents/general/qrcs/setup-mapping-nl.pdf Binary files differindex d661c8706..88a29509c 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-nl.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-nl.pdf diff --git a/doc/context/documents/general/qrcs/setup-mapping-ro.pdf b/doc/context/documents/general/qrcs/setup-mapping-ro.pdf Binary files differindex 5c4f6955b..99826a11a 100644 --- a/doc/context/documents/general/qrcs/setup-mapping-ro.pdf +++ b/doc/context/documents/general/qrcs/setup-mapping-ro.pdf diff --git a/doc/context/documents/general/qrcs/setup-nl.pdf b/doc/context/documents/general/qrcs/setup-nl.pdf Binary files differindex a8b6cde89..2b7277e81 100644 --- a/doc/context/documents/general/qrcs/setup-nl.pdf +++ b/doc/context/documents/general/qrcs/setup-nl.pdf diff --git a/doc/context/documents/general/qrcs/setup-ro.pdf b/doc/context/documents/general/qrcs/setup-ro.pdf Binary files differindex 0117790d3..0cb0f8eb4 100644 --- a/doc/context/documents/general/qrcs/setup-ro.pdf +++ b/doc/context/documents/general/qrcs/setup-ro.pdf diff --git a/doc/context/sources/general/manuals/evenmore/evenmore-libraries.tex b/doc/context/sources/general/manuals/evenmore/evenmore-libraries.tex index 35c957c99..5cca165bb 100644 --- a/doc/context/sources/general/manuals/evenmore/evenmore-libraries.tex +++ b/doc/context/sources/general/manuals/evenmore/evenmore-libraries.tex @@ -183,4 +183,6 @@ distribution (source code) is kept clean. \stopsection +\stopchapter + \stopcomponent diff --git a/doc/context/sources/general/manuals/evenmore/evenmore-whattex.tex b/doc/context/sources/general/manuals/evenmore/evenmore-whattex.tex new file mode 100644 index 000000000..10d3e49f2 --- /dev/null +++ b/doc/context/sources/general/manuals/evenmore/evenmore-whattex.tex @@ -0,0 +1,155 @@ +% language=us + +\startcomponent evenmore-whattex + +\environment evenmore-style + +\startchapter[title={Is \LUAMETATEX\ still \TEX ?}] + +\startsection[title={Introduction}] + +Is \LUAMETATEX\ really a \TEX\ (compatible) engine? The answer to that depends on +how you define \TEX. If you think of the program with the same name, the answer +is definitely \quotation {no}, simply because a program that is not exactly +behaving like \quotation {\TEX\ The Program} cannot be called \TEX. This is why +derived programs have \type {tex} in their name but also some addition that +indicates that it isn't the original: \type {e}, \type {pdf}, \type {lua}. Don't +confuse that with macro package names that have \type {tex} in their name. If you +find such binaries that they are likely some stub to an engine (binary) that +preloads a format file (a memory dump) with the same name. + +When you mean \quotation {\TEX\ The Macro Language} the answer is a bit more +nuanced especially when the results are pretty close to identical. In the next +sections I will discuss this in more detail from the perspective of how \CONTEXT\ +evolved and what engines it has used. + +\stopsection + +\startsection[title={Multiple engines}] + +When we started with \CONTEXT\ there was not that much choice in engines. +Basically one just used original \TEX, but although we used the version that came +with the book, pretty soon we switched to em\TEX, a version that gave more +memory; later a real huge version showed up. The fonts used were bitmaps and the +viewer was a \DVI\ bitmap viewer. However, when our new printer could not be set +up properly we decided to move on to \POSTSCRIPT\ fonts. That also meant using a +different backend driver (\DVIPSONE). And then of course we also started using a +previewer that could handle outline fonts. Once you start along that route +graphics come into play, color shows up and hyperlinks become an option. A couple +of years later the \PDF\ document rendering format was introduced. This paragraph +already mentions a lot of different programs and adaptations, but we're still +talking good old \TEX\ here and \CONTEXT\ was set up in such a way that it +adapted itself to whatever ecosystem made sense. When looking at \TEX\ one has to +consider the front as well as the backend, and both have related primitives and +features. Extensions to the frontend have been driven by the demands of macro +packages (beyond the original ideas) and those of the backend relate to what the +evolving rendering demands impose. + +A couple of decades ago the \ETEX\ project started. It's objective was to extend +stable \TEX\ with a couple of more primitives and features: it is a superset and +therefore still \TEX, but as it really is an extension the name was extended too +(with the bit unusual character $\varepsilon$). At that point the main reason for +\CONTEXT\ was convenience because the new features were already kind of present +in the code base (think of emulated behavior). Again the macro package adapted +itself at runtime. + +Then \PDFTEX\ came around which had some impact. It introduced the concept of a +built|-|in backend that avoided additional programs. The \ETEX\ extensions were +merged into this program so that basically meant that it replaced its +predecessors. For a user \PDFTEX\ was just \TEX. For some reason the narrative +became that \CONTEXT\ depended on \PDFTEX, probably because it was always quick +in using its features, a side effect of being close to the development. + +The \CONTEXT\ package was an early adopter of \METAPOST\ and that graphic +subsystem, although still external, was integrated in such a way that users could +think of it being embedded. This was made possible by the fact that right from +the start \CONTEXT\ came with an infrastructure that handled processing including +subruns as needed for \METAPOST. This is why, years later, adding a \METAPOST\ +library to \LUATEX\ was a logical step. As \CONTEXT\ came with a lot of scripts +(for all kind of tasks related to typesetting and managing a \TEX\ ecosystem) +adding a scripting language (like \LUA) was not that strange either. + +In parallel to \PDFTEX\ the experimental \OMEGA\ program was on its way and +although at some point a stable \ALEPH\ variant was there, it never was robust +enough for production. Its main contribution (that survived) was the introduction +if directional typesetting. There were \CONTEXT\ users using it but for very +specific applications. It's also why the bidirectional model of \OMEGA\ inspired +\LUATEX\ more than the simpler model that \ETEX\ used. + +\stopsection + +\startsection[title={The merge}] + +We now move forward to \LUATEX\ and more precisely \LUAMETATEX\ because that is +for \CONTEXT\ the engine of choice now. To what extend is it \TEX\ or not? The +naive answer is \quotation {no} because some primitives are not present and|/|or +are implemented using \LUA. However, these primitives fall into categories. Some +relate to the backend and in \LUAMETATEX\ the backend is not built|-|in and as a +consequence a macro package has to provide the primitives as part of its +implementation of a backend. This is no big deal because the backend related +primitives in \TEX\ The Program are actually examples of extensions and +implemented as such. Handling them happens in kind of isolated code. Take \type +{\special}: it is basically a no|-|op when the \DVI\ driver doesn't interpret +what is passed to the \DVI\ file. \footnote {\CONTEXT\ \MKII\ has a bunch of +backend drivers, \TEX\ code, that targets specific postprocessors and they hook +into primitives like \type {\special} or the additional \type {\pdf...} ones in +\PDFTEX.} \footnote {We need to keep in mind that by the time \PDFTEX\ and later +\LUATEX\ were developed memory constraints were lifted so these engines didn't +have to work around the limitations that for instance \ETEX\ and \OMEGA\ had to +cope with.} + +A more drastic change is the lack of font loaders and that no fonts can be stored +in the format. Again this relates to the simple fact that todays fonts are more +demanding so we need to extend the machinery and as we do that via \LUA\ +extensions we can as well do all that way. Less drastic, but it could have side +effects, is that the machinery has to be able to deal with \OPENTYPE\ math. And +of course all is \UNICODE\ aware so additional primitives cope with that. But in +principle the old stuff should still work. Hyphenation is also expanded: patterns +are loaded runtime and the hyphenation, ligature building and kerning stages are +split, which actually it a good thing. + +The \LUAMETATEX\ code base is a follow up on \LUATEX, that combines good old +\TEX\ (but adapted with respect to fonts, languages and math as mentioned), parts +of \ETEX\ (so it provides more primitives), bits of \PDFTEX\ (like protrusion and +expansion, although adapted), and rudiments of \OMEGA\ (\ALEPH). And of course +there's a lot of new stuff too, primitives as well as ways to plug in \LUA\ code +plus some helpers at the \LUA\ end. + +As an example of progression, by now the \ETEX\ extensions that we kept are +integrated more naturally in existing subsystems. A nice detail is that there are +no longer any version numbers that relate to \ETEX; for a while they were kept +but suddenly I realized that it makes no sense to waste (four) command codes on +something that is of not much use: there has never been a real \ETEX\ follow up +after its stable release so testing for a version makes no sense. No backend +means no \PDFTEX\ version info too and \OMEGA\ version numbers serve no purpose +either. If a macro package needs to know what functionality is there, testing for +the \LUATEX\ version number, revision and maybe functionality level makes enough +sense. By the way, one reason for a clean up related to \ETEX\ was that where +\ETEX\ uses change files to replace or extend good old \TEX\ code, \LUATEX\ has +one integrated code base. + +\stopsection + +\startsection[title={The verdict}] + +So in the end the answer is that \LUAMETATEX\ is mostly \TEX\ but that due to +developments like for instance \UNICODE, \OPENTYPE\ fonts and math, as well as +the wish to use images, color, runtime graphics, directionality, features beyond +what the engine has built, etc.\ in the end it hopefully meets the demands to +today. In its core the same code is still there although extensions and hooks got +mixed in more naturally. When in documents (or talks) I speak of \TEX\ I +basically refer to a concept (materialized in the set of core primitives and +related functionality) but once extensions come into play I try to talk of +\LUATEX\ or \LUAMETATEX. This happens kind of automatic because I know what got +added but I can imagine that users who entered the game later don't always see +what was added (and when). + +\stopsection + +\stopchapter + +\stopcomponent + +% Written on the day I heard Neal Peart had passed away so mixed with watching +% Rush dvd's which made me realize that times flies. They day before I was at a +% Jan Akkerman show ... timeless quality too. diff --git a/doc/context/sources/general/manuals/evenmore/evenmore.tex b/doc/context/sources/general/manuals/evenmore/evenmore.tex index 317c1548c..293753a79 100644 --- a/doc/context/sources/general/manuals/evenmore/evenmore.tex +++ b/doc/context/sources/general/manuals/evenmore/evenmore.tex @@ -19,6 +19,7 @@ \component evenmore-expansion \component evenmore-macros \component evenmore-libraries + \component evenmore-whattex \stopbodymatter \stopdocument diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-tex.tex b/doc/context/sources/general/manuals/luametatex/luametatex-tex.tex index 4e5a4f584..d02829bea 100644 --- a/doc/context/sources/general/manuals/luametatex/luametatex-tex.tex +++ b/doc/context/sources/general/manuals/luametatex/luametatex-tex.tex @@ -586,8 +586,6 @@ supported commands at this moment are: \starttwocolumns \starttyping -tex.eTeXVersion -tex.eTeXrevision tex.formatname tex.jobname tex.luatexbanner @@ -626,8 +624,6 @@ tex.lastxpos tex.lastypos tex.randomseed tex.luatexversion -tex.eTeXminorversion -tex.eTeXversion tex.currentgrouplevel tex.currentgrouptype tex.currentiflevel |