8 files changed, 426 insertions, 0 deletions
diff --git a/doc/context/presentations/context/2011/context-2011-ebook-export.pdf b/doc/context/presentations/context/2011/context-2011-ebook-export.pdf
new file mode 100644
index 000000000..327a25bd3
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-ebook-export.pdf
diff --git a/doc/context/presentations/context/2011/context-2011-ebook-export.tex b/doc/context/presentations/context/2011/context-2011-ebook-export.tex
new file mode 100644
index 000000000..dfa050ae4
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-ebook-export.tex
@@ -0,0 +1,94 @@
+% \enablemode[print]
+
+\usemodule[present-overlap,abr-02]
+
+\startdocument
+  [title=e-books,
+   subtitle=old wine in new bottles,
+   location=\ConTeXt\ Meeting 2011]
+
+\Topic{Some observations}
+
+\StartSteps
+\startitemize
+\item Most ebooks are just books (or try to be). \FlushStep
+\item Only a small portion has (or needs) design. \FlushStep
+\item To what extent appreciation matters is hard to measure. \FlushStep
+\item Vendor locking is spoiling much. \FlushStep
+\item 10 years of low res screens have made readers tolerant. \FlushStep
+\item Publishers already lost the edge. \FlushStep
+\item Eventually authors will publish themselves. \FlushStep
+\stopitemize
+\StopSteps
+
+% Does quality matter (just look around you)
+% Does livetime matter (much tolerance for potentially crappy old stuff anyway)
+% Does timebound look and feel matter (it helps to put into perspective)
+
+\Topic{What is an ebook}
+
+\StartSteps
+\startitemize
+\item Nicest is it being a \PDF\ (some design). \FlushStep
+\item Easiest is it being an \XHTML\ file (with some \CSS). \FlushStep
+\item Pointless it is being a frozen app. \FlushStep
+\item We can already provide a \PDF\ for paper and screen for quite a while. \FlushStep
+\item We can consider providing an \XHTML\ alongside as reflowable variant. \FlushStep
+\item Who knows what we can provide in the future. \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{The starting point}
+
+\StartSteps
+\startitemize
+\item No output is better than the input. \FlushStep
+\item Fixing bad coding is a waste of energy. \FlushStep
+\item Not that many publishers want to invest in coding. \FlushStep
+\item Not that many tools enforce structure. \FlushStep
+\item The real good devices still have to come but we can be ready for it. \FlushStep
+\item The intelligence has to be in the macro package, not in the engine. \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Implementation}
+
+\StartSteps
+\startitemize
+\item Some users have to produce tagged pdf (to satisfy validators). \FlushStep
+\item It helps that many commands in \CONTEXT\ are built upon a relatively small generic set. \FlushStep
+\item So, given some basic structure, supporting tags is easy. \FlushStep
+\item It integrates in the core. \FlushStep
+\item And as a side effect an export was equally easy to support. \FlushStep
+\item The overhead is not that large (upto 10\%). \FlushStep
+\item Instead of going for freaky solutions (no need for challenges) we assume proper structure. \FlushStep
+\item It's not to hard to extend the current features. \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Consequence for users}
+
+\StartSteps
+\startitemize
+\item Use \type{\startchapter} cum suis, but that was already the \MKIV\ fashion. \FlushStep
+\item Preferable use \type{\startitem} instead of \type {\item}. \FlushStep
+\item Playing safe means tagging paragraphs with \type {\startparagraph}. \FlushStep
+\item Use style environments instead of font switches. \FlushStep
+\item Just use whatever structural markup that \CONTEXT\ already provides for ages. \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{An example}
+
+\StartSteps
+\startitemize
+\item A normal input with \TEX\ commands (cld-mkiv.tex) \FlushStep
+\item Regular (tagged) output (cld-mkiv.pdf) \FlushStep
+\item Structured output (cld-mkiv.xml) \FlushStep
+\item Reflowable output (cld-mkiv-export.xhtml) \FlushStep
+\item Dynamic styling (cld-mkiv-export.css) \FlushStep
+\item Basic template (cld-mkiv-export.template) \FlushStep
+\stopitemize
+\StopSteps
+
+\stopdocument
diff --git a/doc/context/presentations/context/2011/context-2011-mathml-update.pdf b/doc/context/presentations/context/2011/context-2011-mathml-update.pdf
new file mode 100644
index 000000000..b6f00d904
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-mathml-update.pdf
diff --git a/doc/context/presentations/context/2011/context-2011-mathml-update.tex b/doc/context/presentations/context/2011/context-2011-mathml-update.tex
new file mode 100644
index 000000000..fb18ef36a
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-mathml-update.tex
@@ -0,0 +1,67 @@
+\usemodule[present-overlap,abr-02]
+
+\startdocument
+  [title=MathML,
+   subtitle=or math in general,
+   location=\ConTeXt\ Meeting 2011]
+
+\Topic{Some developments}
+
+\StartSteps
+\startitemize
+\startitem \MATHML\ started as an interchange format on the one hand (content) \stopitem \FlushStep
+\startitem but also provides a rendering variant (presentation) \stopitem \FlushStep
+\startitem and in the meantime has been merged with what is called open math \stopitem \FlushStep
+\startitem we now have \MATHML\ 3 and \CONTEXT\ has been updated a while ago to support this \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Some history}
+
+\StartSteps
+\startitemize
+\startitem we supported \MATHML\ right from the start \stopitem \FlushStep
+\startitem in \MKII\ quite some data juggling takes place because we need to do some analysis \stopitem \FlushStep
+\startitem the \MKII\ code has been upgraded a few times but is now frozen \stopitem \FlushStep
+\startitem in \MKIV\ we have rewritten all code using the first version of the new \XML\ parser \stopitem \FlushStep
+\startitem it currently is a mixture of \LUA, \TEX\ and \METAPOST \stopitem \FlushStep
+\startitem there will probably be a partial rewrite some day in the future \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{\UNICODE}
+
+\StartSteps
+\startitemize
+\startitem in the meantime \UNICODE\ has been extended with math  \stopitem \FlushStep
+\startitem in the past in \MATHML\ special characters and symbols were accessed by entity \stopitem \FlushStep
+\startitem but now we can exclusively use \UNICODE\ characters and forget about the entities \stopitem \FlushStep
+\startitem no matter what, we do need to do some analysis on the content of (presentation) elements \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Rendering}
+
+\StartSteps
+\startitemize
+\startitem we still provide rendering options as there might be (cultural) differences \stopitem \FlushStep
+\startitem in both marks we just need to load the module \stopitem \FlushStep
+\startitem in \MKIV\ you need a reasonable namespace directive \stopitem \FlushStep
+\startitem content markup can give better results than presentation markup \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Consequences}
+
+\StartSteps
+\startitemize
+\startitem we already use a database or definitions \stopitem \FlushStep
+\startitem we won't go the (somewhat extreme) route of more commands \stopitem \FlushStep
+\startitem we're working on a subsystem for field driven rendering \stopitem \FlushStep
+\startitem bidirectional math already works but will be integrated in the layout model \stopitem \FlushStep
+\startitem cultural specific solutions are possible (we already provide language specific functions) \stopitem \FlushStep
+\startitem more information is carried around (for rendering as well as export), for instance functions \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\stopdocument
diff --git a/doc/context/presentations/context/2011/context-2011-metapost-how-we-adapt.pdf b/doc/context/presentations/context/2011/context-2011-metapost-how-we-adapt.pdf
new file mode 100644
index 000000000..0f7fef0ee
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-metapost-how-we-adapt.pdf
diff --git a/doc/context/presentations/context/2011/context-2011-metapost-how-we-adapt.tex b/doc/context/presentations/context/2011/context-2011-metapost-how-we-adapt.tex
new file mode 100644
index 000000000..77a9cf993
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-metapost-how-we-adapt.tex
@@ -0,0 +1,104 @@
+% \enablemode[print]
+
+\usemodule[present-overlap,abr-02]
+
+\startdocument
+  [title=MetaPost,
+   subtitle=how we adapt,
+   location=\ConTeXt\ Meeting 2011]
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem we started with simple usage (logos) and \POSTSCRIPT\ output \stopitem \FlushStep
+\startitem then we moved on to conversion to \PDF\ using \TEX\ macro solution \stopitem \FlushStep
+\startitem this has the advantage that fonts are handled by \TEX \stopitem \FlushStep
+\startitem for a long time this was a generic solution (later became the \MKII\ variant) \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem we added some extensions (transparency, cmyk, etc) and \METAFUN\ showed up \stopitem \FlushStep
+\startitem that extension mechanism uses special colors as signals \stopitem \FlushStep
+\startitem we always collected btex ... etex in order to speed up processing \stopitem \FlushStep
+\startitem in addition we added textext and similar features \stopitem \FlushStep
+\startitem communication between \METAFUN\ and \CONTEXT\ became more advanced over time \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem when \LUATEX\ showed up a substitution based lua converter was written \stopitem \FlushStep
+\startitem later when \LPEG\ came around an experimental lpeg converter showed up \stopitem \FlushStep
+\startitem some changes were made to textext processing and run management \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem the arrival of mplib had rather big consequences \stopitem \FlushStep
+\startitem integration of \METAFUN\ became less of a runtime burden \stopitem \FlushStep
+\startitem a more definitive lpeg converter was written \stopitem \FlushStep
+\startitem text handling was kept internal (but still needs two passes) \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem some extensions were changed to use the new pre/postscripts functionality \stopitem \FlushStep
+\startitem the lpeg converter was adapted accordingly \stopitem \FlushStep
+\startitem multiple (independent) \METAPOST\ instances were now supported \stopitem \FlushStep
+\startitem the chemical code was overhauled and moved to the core \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem by now all extensions use pre/postscripts \stopitem \FlushStep
+\startitem this made it easier to add more extend functionality \stopitem \FlushStep
+\startitem again the lpeg converter was adapted (simplified) \stopitem \FlushStep
+\startitem it became possible to do some color trickery with text \stopitem \FlushStep
+\startitem but (till now) color spaces are more complex (mp has a mixed model) \stopitem \FlushStep
+\startitem so we might move towards a slightly different approach \stopitem \FlushStep
+\startitem a couple of helpers were added for Mojca (some more will follow) \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem we're now splitting the code in \MPII\ and \MPIV\ code bases \stopitem \FlushStep
+\startitem from now on the focus will be on \MPIV \stopitem \FlushStep
+\startitem the (rather old) \METAFUN\ code will be cleaned up \stopitem \FlushStep
+\startitem where possible namespaces will be added \stopitem \FlushStep
+\startitem as \METAFUN\ us loaded runtime we see an impact on startup time (quite some files) \stopitem \FlushStep
+\startitem so maybe we will use a packed and/or zipped pseudo format file for faster loading \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Development Stage}
+
+\StartSteps
+\startitemize
+\startitem an overhaul of the flowchart code is on the agenda \stopitem \FlushStep
+\startitem we also want to finish (and cleanup) the chemical related code \stopitem \FlushStep
+\startitem simple data/graphics helpers will be provided (graph replacement) \stopitem \FlushStep
+\startitem and of course we keep moving on (who knows what \METAPOST\ 2 will bring us) \stopitem \FlushStep
+\startitem some examples: tests/mkiv/metapost/plugins-* \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\stopdocument
diff --git a/doc/context/presentations/context/2011/context-2011-sorting-registers.pdf b/doc/context/presentations/context/2011/context-2011-sorting-registers.pdf
new file mode 100644
index 000000000..db0d9da2b
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-sorting-registers.pdf
diff --git a/doc/context/presentations/context/2011/context-2011-sorting-registers.tex b/doc/context/presentations/context/2011/context-2011-sorting-registers.tex
new file mode 100644
index 000000000..f05290906
--- /dev/null
+++ b/doc/context/presentations/context/2011/context-2011-sorting-registers.tex
@@ -0,0 +1,161 @@
+% tests/mkiv/scripts/korean-005.tex
+% examplex elsewhere
+
+% \enablemode[print]
+
+\usemodule[present-overlap,abr-02]
+
+\startdocument
+  [title=Sorting,
+   subtitle=registers,
+   location=\ConTeXt\ Meeting 2011]
+
+\startluacode
+
+local function show(t,start,stop)
+    if type(t) == "table" then
+        start = start or 1
+        stop = stop or #t
+        for i=start,stop do
+            if i > start then
+                context.space()
+            end
+            if type(t[i]) == "number" then
+                context(utf.char(t[i]))
+            else
+                context(t[i])
+            end
+        end
+    elseif type(t) == "string" then
+        context(t)
+    elseif type(t) == "number" then
+        context(utf.char(t))
+    end
+end
+
+function context.ShowCharacterData(n)
+    local d = characters.data[n]
+    if d then
+        local bTR, bTD, eTD, eTR = context.bTR, context.bTD, context.eTD, context.eTR
+        context.bTABLE()
+            bTR() bTD() context("unicode")  eTD() bTD() show(n)                      eTD() eTR()
+            bTR() bTD() context("shcode")   eTD() bTD() show(characters.shchars [n]) eTD() eTR()
+            bTR() bTD() context("lccode")   eTD() bTD() show(characters.lcchars [n]) eTD() eTR()
+            bTR() bTD() context("uccode")   eTD() bTD() show(characters.ucchars [n]) eTD() eTR()
+            bTR() bTD() context("fscode")   eTD() bTD() show(characters.fschars [n]) eTD() eTR() -- leadconsonant
+            bTR() bTD() context("specials") eTD() bTD() show(
+               characters.remap_hangul_syllabe(characters.specials[n]),2) eTD() eTR()
+        context.eTABLE()
+    end
+end
+
+\stopluacode
+
+\unexpanded\def\ShowCharacterData#1{\cldcommand{ShowCharacterData("#1")}}
+
+\Topic{The old way}
+
+\StartSteps
+\startitemize
+\startitem in \MKII\ sorting is delegated to \TEXUTIL\ i.e.\ a multipass action \stopitem \FlushStep
+\startitem encoding vectors are passed along \stopitem \FlushStep
+\startitem sort vectors depend on the language \stopitem \FlushStep
+\startitem there are the usual complications with direct characters and commands \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Moving on}
+
+\StartSteps
+\startitemize
+\startitem in \MKIV\ sorting happens during the run \stopitem \FlushStep
+\startitem we only have to deal with \UNICODE\ (utf) \stopitem \FlushStep
+\startitem sort vectors still depend on the language \stopitem \FlushStep
+\startitem sorting can be controlled by methods \stopitem \FlushStep
+\startitem there is no universal solution (conflicting user demands, mixed languages) \stopitem \FlushStep
+\stopitemize
+\StopSteps
+
+\Topic{Character data}
+
+\setupTABLE[background=color,backgroundcolor=lightgray,rulethickness=.75bp,framecolor=darkgray]
+
+\StartSteps
+\startcombination[5*1]
+    {\definedfont[Normal*none]\ShowCharacterData{a}}            {regular\FlushStep}
+    {\definedfont[Normal*none]\ShowCharacterData{ä}}            {accent\FlushStep}
+    {\definedfont[Normal*none]\ShowCharacterData{æ}}            {ligature\FlushStep}
+    {\definedfont[adobemyungjostd-medium]\ShowCharacterData{그}} {hangul\FlushStep}
+    {\definedfont[adobemyungjostd-medium]\ShowCharacterData{학}} {hangul\FlushStep}
+\stopcombination
+\StopSteps
+
+\Topic{Sorting methods}
+
+\StartSteps
+\starttabulate[|l|l|r|]
+    \NC ch \NC raw character \NC       \FlushStep \NC \NR
+    \NC uc \NC unicode       \NC       \FlushStep \NC \NR
+    \NC mm \NC mapping       \NC minus \FlushStep \NC \NR
+    \NC zm \NC               \NC zero  \FlushStep \NC \NR
+    \NC pm \NC               \NC plus  \FlushStep \NC \NR
+    \NC mc \NC lower case    \NC minus \FlushStep \NC \NR
+    \NC zc \NC               \NC zero  \FlushStep \NC \NR
+    \NC pc \NC               \NC plus  \FlushStep \NC \NR
+\stoptabulate
+\StopSteps
+
+\Topic{Predefined methods}
+
+\StartSteps
+\starttabulate[|l|l|]
+    \NC before \NC mm,mc,uc \NC \NR
+    \NC after  \NC pm,mc,uc \NC \NR
+    \NC first  \NC pc,mm,uc \NC \NR
+    \NC last   \NC mc,mm,uc \NC \NR
+\stoptabulate
+
+\FlushStep
+
+\starttyping
+\enabletrackers[sorters.tests]
+\enabletrackers[sorters.methods]
+\stoptyping
+
+\FlushStep
+\StopSteps
+
+\Topic{An example (1)}
+
+\startbuffer
+àâá\index{àâá}
+aaa\index{aaa}
+aab\index{aab}
+Aaa\index{Aaa}
+Aab\index{Aab}
+\stopbuffer
+
+\StartSteps
+\typebuffer \FlushStep
+
+\startlines \getbuffer \stoplines \FlushStep
+\StopSteps
+
+\Topic{An example (2)}
+
+% \enabletrackers[sorters.tests]
+% \enabletrackers[sorters.methods]
+
+\setupregister[index][criterium=text,n=1,before=,after=]
+\defineframed[indexframed][align=normal,width=.2\textwidth,strut=no]
+
+\StartSteps
+\startcombination[4*1]
+    {\setupinteraction[state=stop]\indexframed{\placeregister[index][method={mm,mc,uc}]}} {mm,mc,uc\FlushStep}
+    {\setupinteraction[state=stop]\indexframed{\placeregister[index][method={pm,mc,uc}]}} {pm,mc,uc\FlushStep}
+    {\setupinteraction[state=stop]\indexframed{\placeregister[index][method={pc,mm,uc}]}} {pc,mm,uc\FlushStep}
+    {\setupinteraction[state=stop]\indexframed{\placeregister[index][method={mc,mm,uc}]}} {mc,mm,uc\FlushStep}
+\stopcombination
+\StopSteps
+
+\stopdocument