8 files changed, 862 insertions, 0 deletions

diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-bits.pdf b/doc/context/presentations/bachotex/2013/bachotex-2013-bits.pdf
new file mode 100644
index 000000000..cadfb197a
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-bits.pdf
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-bits.tex b/doc/context/presentations/bachotex/2013/bachotex-2013-bits.tex
new file mode 100644
index 000000000..96db6bdeb
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-bits.tex
@@ -0,0 +1,223 @@
+% \enablemode[print]
+
+\usemodule[pre-stepwise,present-tiles,abr-02]
+
+\definecolor[maincolor] [darkgray]
+\definecolor[othercolor][r=.3,b=.3]
+
+% \setupinteractionscreen
+%   [option=max]
+
+\startdocument
+  [title={Bits and pieces:\\\\ConTeXt\\MetaPost\\Lua and more},
+   subtitle={Hans Hagen\\EuroBacho\TeX\\May 2013}]
+
+\StartSteps
+
+\starttopic[title={ConTeXt\\recently done}]
+
+    \startitemize
+        \startitem some more cleanup of old left||overs \FlushStep \stopitem
+        \startitem most mechanisms now use the new level of parameter abstraction \FlushStep \stopitem
+        \startitem only a few fundamental incompatibilities (split of mechanisms, more control) \FlushStep \stopitem
+        \startitem slow introduction of hooks and extensions via setups \FlushStep \stopitem
+        \startitem first version of new multi|| column routines \FlushStep \stopitem
+        \startitem replacing mechanism that have a (too) complex implementation \FlushStep \stopitem
+        \startitem exploring the mix (e.g. chemistry with Alan) \FlushStep \stopitem
+        \startitem remove some ugly left||overs from \MKII\ math \FlushStep \stopitem
+        \startitem normalized dynamic fonts (mostly interfacing) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={ConTeXt\\next on the todo list}]
+
+    \startitemize
+        \startitem more definitive split between generic and context (generated) \FlushStep \stopitem
+        \startitem some math extensions, maybe already math dictionaries \FlushStep \stopitem
+        \startitem normalize all styles and modules \FlushStep \stopitem
+        \startitem play a bit more with the \LUA\ parbuilder \FlushStep \stopitem
+        \startitem add more integrated bidi layout support \FlushStep \stopitem
+        \startitem finalize experimental (auto)script code \FlushStep \stopitem
+        \startitem investigate what more is needed in the \CLD\ interface \FlushStep \stopitem
+        \startitem check multi||lingual interface translations (not entirely in sync now) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={MetaPost\\recently done}]
+
+    \startitemize
+        \startitem we already had instances, a bit more configurability added \FlushStep \stopitem
+        \startitem instances now can be initialized to a number model \FlushStep \stopitem
+        \startitem some of the (runtime loaded) \METAFUN\ code has been optimized (as \METAPOST\ has become somewhat slower and now has dynamic memory management \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={MetaPost\\next on the todo list}]
+
+    \startitemize
+        \startitem reimplement and extend graph (with Alan) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Lua\\recently done}]
+
+    \startitemize
+        \startitem font code has been better isolated \FlushStep \stopitem
+        \startitem basic modules are more or less stable now \FlushStep \stopitem
+        \startitem support for \SQL, templates and other workflow helper code \FlushStep \stopitem
+        \startitem the \CLD\ manual has been extended (continuous effort) \FlushStep \stopitem
+        \startitem messages and tracing have been checked and made more consistent \FlushStep \stopitem
+        \startitem it is possible to build libraries so that one can use the same kind of code in projects (\type {mtxrun} using \LUATEX\ vs \type {mtxlibs} using \LUA) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Lua\\next on the todo list}]
+
+    \startitemize
+        \startitem maybe cleanup of file database code (no real need to be completely \type {kpse} and \TDS\ compatible) \FlushStep \stopitem
+        \startitem pick up run||from|||zip experiment \FlushStep \stopitem
+        \startitem maybe more some framework code in the distribution \FlushStep \stopitem
+        \startitem experiment with some libraries (sockets, graphics, \type {gsl}) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Lua\TeX\\recently done}]
+
+    \startitemize
+        \startitem
+            Luigi cooked up \LUAJITTEX\ and we did lots of experiments \unknown\
+            our pet project turned into an persistent extra engine \unknown\ some
+            10 upto 40\% speedup due to faster \LUA\ interpreter (no \type {jit})
+        \FlushStep \stopitem
+        \startitem
+            I prototyped some speedups with access to node properties \unknown\
+            Luigi and I tested this across platforms \unknown\ and Taco finalized
+            and integrated all into the codebase
+        \FlushStep \stopitem
+        \startitem
+            Taco did the periodical check of tracker items \unknown\ some not too
+            intrusive patches and fixes have been applied \unknown\ the new
+            \METAPOST\ library has been integrated.
+        \FlushStep \stopitem
+        \startitem
+            I played with a speedup of logging to the console and identified some
+            bottlenecks \unknown\ Taco decided to make some improvements in the
+            code base.
+        \FlushStep \stopitem
+        \startitem
+            I did some parbuilder experiments in \CONTEXT\ with simplified hz
+            \unknown\ trivial extension needed in backend \unknown\ in the
+            meantime Hartmut decided to drastically cleanup the whole code path.
+        \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Lua\TeX\\next on the todo list}]
+
+    \startitemize
+        \startitem remove some old engine stuff (after tl 2013 is out) \FlushStep \stopitem
+        \startitem with Luigi, get \SWIGLIB\ project upto speed (and running) \FlushStep \stopitem
+        \startitem with Hartmut, get ex||factor implemented in the backend (explored in the \LUA\ parbuilder) \FlushStep \stopitem
+        \startitem with Taco, catch up on some ideas we have accumulated \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Fonts\\next on the todo list}]
+
+    \startitemize
+        \startitem normalize a few extensions \FlushStep \stopitem
+        \startitem implement some more detailed control \FlushStep \stopitem
+        \startitem play with the \LUA\ parbuilder (if it makes sense at all) \FlushStep \stopitem
+        \startitem finish (and test) support for Devanagari \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Manuals]
+
+    \startitemize
+        \startitem new manuals for templates, \SQL, \SCITE, extreme tables, etc. \FlushStep \stopitem
+        \startitem first uploads of the (technical) font manual \FlushStep \stopitem
+        \startitem package some sources to the documentation zip \FlushStep \stopitem
+    \stopitemize
+
+    todo:
+
+    \startitemize
+        \startitem check metafun for additions \FlushStep \stopitem
+        \startitem check and extend the \XML\ manual \FlushStep \stopitem
+        \startitem check and republish the mathml manual \FlushStep \stopitem
+        \startitem redo some of the specific manuals for \MKIV \FlushStep \stopitem
+        \startitem beginners manual is being redone (by Ton) \FlushStep \stopitem
+        \startitem chemistry manual is being redone (by Alan) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Scripts]
+
+    \startitemize
+        \startitem additional help info support (\TEXLIVE\ requirement) \FlushStep \stopitem
+        \startitem relatively stable but most are still a first||version \FlushStep \stopitem
+        \startitem improve the \SCITE\ reference lexers \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\starttopic[title=Speed]
+
+\goto{pre-bt-2013-speed}[file(pre-bt-2013-speed)] \FlushStep
+
+\stoptopic
+
+\stopdocument
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-luatex.pdf b/doc/context/presentations/bachotex/2013/bachotex-2013-luatex.pdf
new file mode 100644
index 000000000..147c34ac3
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-luatex.pdf
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-luatex.tex b/doc/context/presentations/bachotex/2013/bachotex-2013-luatex.tex
new file mode 100644
index 000000000..1dc6f2f89
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-luatex.tex
@@ -0,0 +1,205 @@
+% \enablemode[print]
+
+\usemodule[pre-stepwise,present-tiles,abr-02]
+
+\definecolor[maincolor] [darkgray]
+\definecolor[othercolor][g=.3,b=.3]
+
+% \setupinteractionscreen
+%   [option=max]
+
+\setupbodyfont[opendyslexic,ss]
+
+\startdocument
+  [title={Lua\TeX\ for dummies\\\\(so you can still leave)},
+   subtitle={Hans Hagen\\EuroBacho\TeX\\May 2013}]
+
+\StartSteps
+
+\starttopic[title={The \TEX\ perspective}]
+
+    \startitemize
+        \startitem it started out as \PDFTEX \FlushStep \stopitem
+        \startitem then got merged with \ALEPH \FlushStep \stopitem
+        \startitem but we left out the ugly bits of both \FlushStep \stopitem
+        \startitem it's exclusively \UTF-8 \FlushStep \stopitem
+        \startitem it's math machinery got extended with \OPENTYPE\ like features \FlushStep \stopitem
+        \startitem there are no fundamental extensions as it's impossible to agree in them \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={The \LUA\ perspective}]
+
+    \startitemize
+        \startitem it just a \LUA\ engine \FlushStep \stopitem
+        \startitem it has some extra libraries on board \FlushStep \stopitem
+        \startitem you don't even have to use \TEX \FlushStep \stopitem
+        \startitem but there are hooks into the \TEX\ machinery \FlushStep \stopitem
+        \startitem and we can go further by loading libraries \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={The hybrid perspective}]
+
+    \startitemize
+        \startitem we can extend \TEX\ using \LUA \FlushStep \stopitem
+        \startitem eventually everything will be opened up \FlushStep \stopitem
+        \startitem users never have to see any of that \FlushStep \stopitem
+        \startitem they can simply use \LUA\ for scripting and print results to \TEX \FlushStep \stopitem
+        \startitem but developers can go deep into the \TEX\ internals and mess around \FlushStep \stopitem
+        \startitem the average user will just depend on what a macro package will provide \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={The complications}]
+
+    \startitemize
+        \startitem normally one wants a bit of infrastructure (management) \FlushStep \stopitem
+        \startitem and maybe a special user space, hidden from core extensions \FlushStep \stopitem
+        \startitem but history has tought that users can't be controlled that way \FlushStep \stopitem
+        \startitem so we stick to just providing the mechanisms \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={The future}]
+
+    \startitemize
+        \startitem there are a couple of generic modules (derived from \CONTEXT) \FlushStep \stopitem
+        \startitem in principle I can make more generic modules \FlushStep \stopitem
+        \startitem that's after all the idea behind the (to be) \METATEX\ variant \FlushStep \stopitem
+        \startitem but does it really make sense as one still needs substantial subsystems \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={This workshop}]
+
+    \startitemize
+        \startitem just using \LUA: it's what most users will do \FlushStep \stopitem
+        \startitem showing the hooks: it's what developers want to use \FlushStep \stopitem
+        \startitem answering questions: it's probably the most I can do \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Just plain}]
+
+    We need to make a format, like:
+
+    \starttyping
+    luatex --ini plain \dump
+    \stoptyping
+
+    \FlushStep
+
+    and can then run files with:
+
+    \starttyping
+    luatex --fmt=plain somefile.tex
+    \stoptyping
+
+    \FlushStep
+
+    This is a another way:
+
+    \starttyping
+    mtxrun --script plain --make --texformat=plain
+    \stoptyping
+
+    \FlushStep
+
+    with:
+
+    \starttyping
+    mtxrun --script plain --texformat=plain somefile.tex
+    \stoptyping
+
+    \FlushStep
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={A bit less plain}]
+
+    In order to profit from \OPENTYPE\ fonts:
+
+    \starttyping
+    mtxrun --script plain --make
+    \stoptyping
+
+    \FlushStep
+
+    with:
+
+    \starttyping
+    mtxrun --script plain somefile.tex
+    \stoptyping
+
+    \FlushStep
+
+    On windows you can copy \type {mtxrun.exe} to \type {plain.exe} and stick to:
+
+    \starttyping
+    plain --make
+    \stoptyping
+
+    \FlushStep
+
+    with:
+
+    \starttyping
+    plain somefile.tex
+    \stoptyping
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Hardly plain}]
+
+    If you can live with a bit less plain:
+
+    \starttyping
+    context yourfile.tex
+    \stoptyping
+
+    \FlushStep
+
+\stoptopic
+
+\StopSteps
+
+\stopdocument
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-sense.pdf b/doc/context/presentations/bachotex/2013/bachotex-2013-sense.pdf
new file mode 100644
index 000000000..be0939b40
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-sense.pdf
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-sense.tex b/doc/context/presentations/bachotex/2013/bachotex-2013-sense.tex
new file mode 100644
index 000000000..72e3f4dc2
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-sense.tex
@@ -0,0 +1,319 @@
+% \enablemode[print]
+
+\usemodule[pre-stepwise,present-tiles,abr-02]
+
+\definecolor[maincolor] [s=.6]
+\definecolor[othercolor][s=.2]
+
+% \setupinteractionscreen
+%   [option=max]
+
+\startdocument
+  [title={How about those\\typographic virtues:\\do they still make sense?},
+   subtitle={Hans Hagen\\EuroBacho\TeX\\May 2013}]
+
+\StartSteps
+
+\starttopic[title=Typesetting]
+
+    \FlushStep
+
+    \startitemize
+        \startitem somehow we turned sounds into speech into language \FlushStep \stopitem
+        \startitem and after that it may have started with writing in the sand \FlushStep \stopitem
+        \startitem followed by painting on cave walls \FlushStep \stopitem
+        \startitem or maybe carving symbols in wood \FlushStep \stopitem
+        \startitem and figuring out some writing system \FlushStep \stopitem
+        \startitem that made it possible to chisel thoughts in stone \FlushStep \stopitem
+        \startitem and eventually putting blobs on paper \FlushStep \stopitem
+        \startitem that we somehow managed to map onto pixels \FlushStep \stopitem
+    \stopitemize
+
+    but \FlushStep
+
+    \startitemize
+        \startitem typesetting only happened very lately \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=In the process]
+
+    \FlushStep
+
+    \startitemize
+        \startitem mankind optimized the basic shapes (to suit the language) \FlushStep \stopitem
+        \startitem and kept inventing new symbols \FlushStep \stopitem
+        \startitem more and more automated typesetting and rendering and printing \FlushStep \stopitem
+        \startitem and of course this went with all kind of silly arguments \FlushStep \stopitem
+    \stopitemize
+
+    think of this: \FlushStep
+
+    \startitemize
+        \startitem for ages scribes were the only way to get high end arabic typesetting \FlushStep \stopitem
+        \startitem and now we can do this mostly automatic (in good and bad ways) \FlushStep \stopitem
+        \startitem so we endangered yet another craft  \FlushStep \stopitem
+    \stopitemize
+
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=But eventually]
+
+    \FlushStep
+
+    \startitemize
+        \startitem new interfaces will bring new ways of reading (how about leap motion) \FlushStep \stopitem
+        \startitem and we'll go from manual to visual (glasses, look at gaming) \FlushStep \stopitem
+        \startitem so information will be pushed more or less directly into our brain \FlushStep \stopitem
+        \startitem while high quality rendering moves to the arts department \FlushStep \stopitem
+        \startitem and in the end probably not much gets printed any more \FlushStep \stopitem
+        \startitem so we will share, stare at and discuss books no longer the way we do now \FlushStep \stopitem
+        \startitem just look at how kids deal with information nowadays \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Targeting paper]
+
+    \FlushStep
+
+    \startitemize
+        \startitem we kept trying to save space by combine shapes and using umlauts and accents \FlushStep \stopitem
+        \startitem we can make it look better, using ligatures, alternative shapes \FlushStep \stopitem
+        \startitem color comes cheap, as does mixing fonts \FlushStep \stopitem
+        \startitem went from left to right and vise versa and top to bottom and mixed all this \FlushStep \stopitem
+        \startitem papers and magazines squeezed more into columns (in fact, we get less newspapers and magazines, but more advertising, so for a while there's as much print but more of dubious quality) \FlushStep \stopitem
+        \startitem and we even optimized the art of unreadability as in anti||smoke warnings \FlushStep \stopitem
+        \startitem thanks to software we can tweak fonts, mess with kerning, fool ourselve with expansion and protrusion \FlushStep \stopitem
+        \startitem we mess around with margins, aspect ratios, scaling, rotating, and justification \FlushStep \stopitem
+        \startitem and yes, we introduced conventions but also entered endless debates \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Towards displays]
+
+    \FlushStep
+
+    \startitemize
+        \startitem nowadays we can fake the old stuff on the screen and simulate paper \FlushStep \stopitem
+        \startitem we have weird user interfaces as we still want to recognize the old e.g.\ funny borders and strange buttons \FlushStep \stopitem
+        \startitem and we're told how less pixels are actually needed to keep us happy \FlushStep \stopitem
+        \startitem while we stare at ourselves on those mirroring and radiating displays \FlushStep \stopitem
+        \startitem lack of detail gets nicely compensated with special reading compensation programs at school \FlushStep \stopitem
+        \startitem and still progress is hampered by copyrighting trivial properties and inventions that anyone can come up with given the machinery \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=The state of affairs]
+
+    \FlushStep
+
+    \startitemize
+        \startitem we already lost (or maybe never reached) optimal quality \FlushStep \stopitem
+        \startitem it looks like ragged right won the battle \FlushStep \stopitem
+        \startitem and messing with fonts beyond what designers had in mind is okay \FlushStep \stopitem
+        \startitem the users start controlling the layout by scaling, rotating and setting properties \FlushStep \stopitem
+    \stopitemize
+
+    so \FlushStep
+
+    \startitemize
+        \startitem why do we texies still bother about typography, hobyism apart \FlushStep \stopitem
+        \startitem does paying so much attention and trying to be original still fit into rappidly changing times \FlushStep \stopitem
+        \startitem we're not alone: the same is true for programs, apps, operating systems, etc \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Take ligatures]
+
+    \FlushStep
+
+    \definefont[TestA][texgyrepagella-regular*default]
+    \definefont[TestB][cambria*default]
+    \definefont[TestC][dejavuserif*default]
+    \definefont[TestD][lmroman10-regular*default]
+
+    \startcombination[alternative=none,nx=1,ny=4]
+        {\hbox to \textwidth{\scale[height=.1\textheight]{\TestA fi ffi fl ffl ij}\hss}}
+        {\hbox to \textwidth{\scale[height=.1\textheight]{\TestB fi ffi fl ffl ij}\hss\tlap{\scale[height=.25\textheight]{\TestB ffl\hskip.1emffi}}}}
+        {\hbox to \textwidth{\scale[height=.1\textheight]{\TestC fi ffi fl ffl ij}\hss}}
+        {\hbox to \textwidth{\scale[height=.1\textheight]{\TestD fi ffi fl ffl ij}\hss\tlap{\scale[height=.25\textheight]{\TestD ffl\hskip.1emffi}}}}
+    \stopcombination
+
+    \FlushStep
+
+    Subtle kerning, partial substitution, different shapes: take your
+    choice. Can texies really claim that their ffi looks the best? Just
+    stare at it for a while.
+
+    \FlushStep
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Accent battles]
+
+    \FlushStep
+
+    \startcombination[alternative=label,nx=5,ny=2]
+        {\scale[height=.25\textheight]{\definedfont[texgyrepagella-regular]š}}
+        {\scale[height=.25\textheight]{\definedfont[dejavuserif]š}}
+        {\scale[height=.25\textheight]{\definedfont[cambria]š}}
+        {\scale[height=.25\textheight]{\definedfont[texgyretermes-regular]š}}
+        {\scale[height=.25\textheight]{\definedfont[lucidabrightot]š}}
+        {\scale[height=.25\textheight]{\definedfont[texgyrebonum-regular]š}}
+        {\scale[height=.25\textheight]{\definedfont[texgyreheros-regular]š}}
+        {\scale[height=.25\textheight]{\definedfont[lmroman10-regular]š}}
+        {\scale[height=.25\textheight]{\definedfont[KozMinPr6N-Regular]š}}
+        {\scale[height=.25\textheight]{\definedfont[zapfinoextraltpro]š}}
+    \stopcombination
+
+    \FlushStep
+
+    \blank
+
+    Of course there are some conventions, but given that designs are \unknown\ well,
+    designs \unknown\ it's never going to be okay for all of us.
+
+    \FlushStep
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Justification]
+
+    \FlushStep
+
+  % \externalfigure[chinese-courier.jpg][height=.7\textheight]
+    \externalfigure[chinese-courier.jpg][width=\textwidth]
+
+    \FlushStep
+
+    \blank
+
+    Intercharacter spacing, interglyph spacing, tightening symbols: why bother
+    any longer: let's play safe and from now on advice to use monospaced ragged
+    right.
+
+    \FlushStep
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Backslashes]
+
+    \FlushStep
+
+    \startitemize
+        \startitem you always need a way to escape formatting directives \FlushStep \stopitem
+        \startitem so texies have the backslash and a few more special characters \FlushStep \stopitem
+        \startitem coding in \XML\ seems to be too complex and awkward for most users \FlushStep \stopitem
+        \startitem but \ASCII\ based quick and dirty formatting becomes a fashion (\type {*doc}) \FlushStep \stopitem
+        \startitem of course influencing the makeup and making things nice involves even nastier escapes \FlushStep \stopitem
+        \startitem and in the process we eventually loose quality \FlushStep \stopitem
+    \stopitemize
+
+    but \FlushStep
+
+    \startitemize
+        \startitem it fits nicely into quick and dirty often one||time markup \FlushStep \stopitem
+        \startitem and real markup, maybe targeted at reuse, becomes a speciality, craft, hobby or disappears \FlushStep \stopitem
+        \startitem there is no reason why what we do now stays \unknown\ we have no copying monks left either \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=Endangered features]
+
+    \FlushStep
+
+    \startitemize
+        \startitem ebooks are mostly single sided \FlushStep \stopitem
+        \startitem but somehow we still care about pages (or can't look beyond them) \FlushStep \stopitem
+        \startitem there is no longer room and need for multi||columns \FlushStep \stopitem
+        \startitem and also no need for footnotes as we can have roll||overs \FlushStep \stopitem
+        \startitem paper size can still be different but can swap to landscape\FlushStep \stopitem
+        \startitem floats become cumbersome compared to paper books, so no floats \FlushStep \stopitem
+        \startitem margins, they waste space and we already have hardware margins \FlushStep \stopitem
+        \startitem a proper tables of contents still make some sense \FlushStep \stopitem
+        \startitem indices can be replaced but searching in most cases \FlushStep \stopitem
+        \startitem bibliographies can become pop||ups \FlushStep \stopitem
+        \startitem readers are encouraged to choose and scale fonts so the design has limitations \FlushStep \stopitem
+        \startitem and why even bother optimizing the look and feel \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title=The future of \TEX]
+
+    \FlushStep
+
+    \startitemize
+        \startitem as it happens: these are all mechanisms that complicate the \TEX\ machinery and workflow \FlushStep \stopitem
+        \startitem and removing the need for them might as well remove the need for \TEX \FlushStep \stopitem
+        \startitem but still, for a long time \CONTEXT\ \MKIV\ can fulfill the needs as demands probably only become more simple \FlushStep \stopitem
+        \startitem and I can start working on a simple version: twittertex™, monospaced, one paragraph fat most 140 characters, no pages, no structure, maybe random generated content, etc. \FlushStep \stopitem
+        \startitem or maybe first make some intermediate version: markuptex™, geared at ebooks in some kind of \XML\ format \FlushStep \stopitem
+        \startitem and Luigi will make \type {livetex}, a dna based typesetting plugin that connects to our already built||in retina \FlushStep \stopitem
+    \stopitemize
+
+    however, \FlushStep
+
+    \startitemize
+        \startitem looking at the still active \TEX\ crowd we will stay around for a while \FlushStep \stopitem
+        \startitem given that we manage to advocate the virtues of typographical traditions \FlushStep \stopitem
+        \startitem and for that, we might need to reinvent ourselves (a nice theme for a conference) \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\stopdocument
+
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-speed.pdf b/doc/context/presentations/bachotex/2013/bachotex-2013-speed.pdf
new file mode 100644
index 000000000..6dcd5478c
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-speed.pdf
diff --git a/doc/context/presentations/bachotex/2013/bachotex-2013-speed.tex b/doc/context/presentations/bachotex/2013/bachotex-2013-speed.tex
new file mode 100644
index 000000000..df7ca2f3a
--- /dev/null
+++ b/doc/context/presentations/bachotex/2013/bachotex-2013-speed.tex
@@ -0,0 +1,115 @@
+% \enablemode[print]
+
+\usemodule[pre-stepwise,present-tiles,abr-02]
+
+\definecolor[maincolor] [darkgray]
+\definecolor[othercolor][r=.3,g=.3]
+
+% \setupinteractionscreen
+%   [option=max]
+
+\setupbodyfont[15pt]
+
+\startdocument
+  [title={Speed:\\\\can we make\\it any faster},
+   subtitle={Hans Hagen\\EuroBacho\TeX\\May 2013}]
+
+\StartSteps
+
+\starttopic[title={Speed}]
+
+    \startitemize
+        \startitem speed matters in a edit-run-preview cycle although this is mostly perception \FlushStep \stopitem
+        \startitem the nicer the interface, the slower it gets, but you seldom set something up \FlushStep \stopitem
+        \startitem everything you provide gets used at some point, also in inefficient ways \FlushStep \stopitem
+        \startitem lots of local (grouped) tweaks leads to many mechanisms kicking in unseen \FlushStep \stopitem
+        \startitem wrong use of functionality can have drastic and unexpected speed penalties \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={Pages per minute}]
+
+    \startitemize
+        \startitem we try to speed up baseline performance (in pages per second) \FlushStep \stopitem
+        \startitem identify and optimize critical routines, both at the \TEX\ and \LUA\ end \FlushStep \stopitem
+        \startitem of course the machine (Dell M90, SSD, 4GB, 2.33 Ghz T7600, Windows 8) and versions if \LUATEX\ (0.72+) and \CONTEXT\ matter \FlushStep \stopitem
+    \stopitemize
+
+    \blank
+
+    \starttyping
+    \dorecurse {1000} {test \page}
+    \stoptyping
+
+    \FlushStep
+
+    \blank
+
+    \starttabulate[|r|r|r|r|]
+    \HL
+    \NC \bf \# pages \NC \bf Januari \NC \bf April \NC \bf May\rlap{\quad(2013)} \NR
+    \HL
+    \NC     1 \NC   2 \NC   2 \NC   2 \NC \NR
+    \NC    10 \NC  15 \NC  17 \NC  17 \NC \NR
+    \NC   100 \NC  90 \NC 109 \NC 110 \NC \NR
+    \NC  1000 \NC 185 \NC 234 \NC 259 \NC \NR
+    \NC 10000 \NC 215 \NC 258 \NC 289 \NC \NR
+    \HL
+    \stoptabulate
+
+    \FlushStep
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={What happens}]
+
+    \startitemize
+        \startitem load macros and \LUA\ code is loaded from the format \FlushStep \stopitem
+        \startitem the system gets initialized, think of fonts and languages \FlushStep \stopitem
+        \startitem additional (runtime) files are loaded \FlushStep \stopitem
+        \startitem text is typeset and eventually gets passed to the page builder \FlushStep \stopitem
+        \startitem pages are packaged, this includes reverting to global document states \FlushStep \stopitem
+        \startitem the \PDF\ representation is created \FlushStep \stopitem
+        \startitem each of these steps has its bottlenecks \FlushStep \stopitem
+        \startitem the more we don, the more \LUA\ gets involved \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\StartSteps
+
+\starttopic[title={What we can do}]
+
+    \startitemize
+        \startitem avoid copying boxes where possible \FlushStep \stopitem
+        \startitem only enable initializers and finalizers when functionality is used \FlushStep \stopitem
+        \startitem be clever with fonts, in usage as well as in supporting features \FlushStep \stopitem
+        \startitem use trial runs in multi||pass mechanisms \FlushStep \stopitem
+        \startitem avoid too much macro expansion (only matters for tracing) \FlushStep \stopitem
+        \startitem accept that more functionality has a price \FlushStep \stopitem
+    \stopitemize
+
+    but
+
+    \startitemize
+        \startitem don't compromise functionality \FlushStep \stopitem
+        \startitem avoid too obscure code \FlushStep \stopitem
+        \startitem forget about optimization by means of combining functionality \FlushStep \stopitem
+    \stopitemize
+
+\stoptopic
+
+\StopSteps
+
+\stopdocument