Source Browser ?

1\usemodule[present-overlap,abr-02]
2
3\startdocument
4  [title=MathML,
5   subtitle=or math in general,
6   location=\ConTeXt\ Meeting 2011]
7
8\Topic{Some developments}
9
10\StartSteps
11\startitemize
12\startitem \MATHML\ started as an interchange format on the one hand (content) \stopitem \FlushStep
13\startitem but also provides a rendering variant (presentation) \stopitem \FlushStep
14\startitem and in the meantime has been merged with what is called open math \stopitem \FlushStep
15\startitem we now have \MATHML\ 3 and \CONTEXT\ has been updated a while ago to support this \stopitem \FlushStep
16\stopitemize
17\StopSteps
18
19\Topic{Some history}
20
21\StartSteps
22\startitemize
23\startitem we supported \MATHML\ right from the start \stopitem \FlushStep
24\startitem in \MKII\ quite some data juggling takes place because we need to do some analysis \stopitem \FlushStep
25\startitem the \MKII\ code has been upgraded a few times but is now frozen \stopitem \FlushStep
26\startitem in \MKIV\ we have rewritten all code using the first version of the new \XML\ parser \stopitem \FlushStep
27\startitem it currently is a mixture of \LUA, \TEX\ and \METAPOST \stopitem \FlushStep
28\startitem there will probably be a partial rewrite some day in the future \stopitem \FlushStep
29\stopitemize
30\StopSteps
31
32\Topic{\UNICODE}
33
34\StartSteps
35\startitemize
36\startitem in the meantime \UNICODE\ has been extended with math  \stopitem \FlushStep
37\startitem in the past in \MATHML\ special characters and symbols were accessed by entity \stopitem \FlushStep
38\startitem but now we can exclusively use \UNICODE\ characters and forget about the entities \stopitem \FlushStep
39\startitem no matter what, we do need to do some analysis on the content of (presentation) elements \stopitem \FlushStep
40\stopitemize
41\StopSteps
42
43\Topic{Rendering}
44
45\StartSteps
46\startitemize
47\startitem we still provide rendering options as there might be (cultural) differences \stopitem \FlushStep
48\startitem in both marks we just need to load the module \stopitem \FlushStep
49\startitem in \MKIV\ you need a reasonable namespace directive \stopitem \FlushStep
50\startitem content markup can give better results than presentation markup \stopitem \FlushStep
51\stopitemize
52\StopSteps
53
54\Topic{Consequences}
55
56\StartSteps
57\startitemize
58\startitem we already use a database or definitions \stopitem \FlushStep
59\startitem we won't go the (somewhat extreme) route of more commands \stopitem \FlushStep
60\startitem we're working on a subsystem for field driven rendering \stopitem \FlushStep
61\startitem bidirectional math already works but will be integrated in the layout model \stopitem \FlushStep
62\startitem cultural specific solutions are possible (we already provide language specific functions) \stopitem \FlushStep
63\startitem more information is carried around (for rendering as well as export), for instance functions \stopitem \FlushStep
64\stopitemize
65\StopSteps
66
67\stopdocument
68