diff options
author | Karl Berry <karl@freefriends.org> | 2017-04-19 23:04:15 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2017-04-19 23:04:15 +0000 |
commit | f74161ca4e7eb3c5af9afcbe92522ae3b58987c1 (patch) | |
tree | 3c30a13df5ac7968195c85070a2b074578e669d2 /Master/texmf-dist/doc/context/presentations/bachotex/2016 | |
parent | 1d5a55ac8f5506a7ae9cfca52f4b588182e199d4 (diff) |
context beta/cont-tmf.zip (Apr 16 12:55)
git-svn-id: svn://tug.org/texlive/trunk@43931 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/context/presentations/bachotex/2016')
-rw-r--r-- | Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.pdf | bin | 0 -> 40433 bytes | |||
-rw-r--r-- | Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.tex | 631 | ||||
-rw-r--r-- | Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.pdf | bin | 0 -> 52712 bytes | |||
-rw-r--r-- | Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.tex | 212 |
4 files changed, 843 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.pdf b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.pdf Binary files differnew file mode 100644 index 00000000000..cacdc4c56ce --- /dev/null +++ b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.pdf diff --git a/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.tex b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.tex new file mode 100644 index 00000000000..aa9cb60fde3 --- /dev/null +++ b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-opentype.tex @@ -0,0 +1,631 @@ +\usemodule[present-banner] + +\startdocument + [title={OPENTYPE FONTS}, + subtitle={the generic loader}, + location={Hans Hagen \endash\ bacho\TeX\ 2016}] + +\starttitle[title={how engines sees a font}] + +\startsubject[title={\TeX}] + + \highlight [nb] {fields:} width, height, depth, italic correction, kern table, + ligature tree, vf commands, next size pointer, extensible specification + \highlight [nb] {and} a set of text and math parameters + +\stopsubject + +\startsubject[title={\pdfTeX}] + + \highlight [nb] {extra fields:} left protruding, right protruding, expansion + factor \highlight [nb] {and} parameters to control these + +\stopsubject + +\startsubject[title={\LuaTeX}] + + \highlight [nb] {extra fields:} math top accent, math bot accent, tounicode, + adapted extensible specification, vertical variants, horizontal variants, + name, index, used status, math kerns \highlight [nb] {and} extra parameters + \highlight [nb] {and} math constants \highlight [nb] {and} no 8~bit + limitations + +\stopsubject + +\startsubject[title={\XeTeX}] + + probably something similar + +\stopsubject + +\stoptitle + +\starttitle[title={font handling}] + +\startsubject[title={loading opentype font data}] + + \startitemize + \startitem + till recently we used the built|-|in fontforge loader library + \stopitem + \startitem + but now we use a recently written \Lua\ loader + \stopitem + \startitem + but use a similar feature handler + \stopitem + \startitem + in \ConTeXt\ one can fall back to the old loader/handler + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={applying (opentype) features}] + + \highlight [nb] {generic modes:} base, node \crlf + \highlight [nb] {\ConTeXt\ modes:} base, node, auto, dynamic + +\stopsubject + +\startsubject[title={locating (opentype) fonts}] + + \startitemize + \startitem + \highlight [nb] {file}: kpse in generic, resolvers in \ConTeXt + \stopitem + \startitem + \highlight [nb] {name}: simple in generic, extended in \ConTeXt, + different in \LaTeX + \stopitem + \startitem + \highlight [nb] {spec}: not in generic (uses font database) + \stopitem + \startitem + \highlight [nb] {virtual}: not in generic + \stopitem + \startitem + \highlight [nb] {lua}: delegated to low level interfaces + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={preparations}] + +\startsubject[title={after loading}] + + \startitemize + \startitem + initialize format driven substitution + \stopitem + \startitem + initialize format driven positioning + \stopitem + \startitem + enable analysis of states/properties + \stopitem + \startitem + initialize additional data for engine (protrusion, expansion, extend, + slant) + \stopitem + \startitem + apply user or \TeX\ format extensions + \stopitem + \startitem + apply manipulations before and after loading + \stopitem + \startitem + (build virtual fonts) + \stopitem + \startitem + enable special script handlers (fuzzy side of opentype) + \stopitem + \startitem + pass metrics and some metadata to \TeX + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={benefit}] + + efficient access to all font properties for additional processing beforehand + or afterwards + +\stopsubject + +\stoptitle + +\starttitle[title={processing}] + +\startsubject[title={steps}] + + \startitemize + \startitem + (comes after hyphenation) + \stopitem + \startitem + first identifies to be handled modes + \stopitem + \startitem + normalization (in \ConTeXt) node list + \stopitem + \startitem + delegate handling to \TeX\ or \Lua + \stopitem + \startitem + when using \Lua\ features are applied in prescribed order: + substitution, positioning, etc. + \stopitem + \startitem + as last step positioning is finalized (left/right kern injection, + space kerning, anchoring, cursives) + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={remarks}] + + \startitemize + \startitem + efficient contextual analysis is|-|non trivial + \stopitem + \startitem + discretionaries need special care: ...pre ...replace... post... + \stopitem + \startitem + there is no real limit in extensions + \stopitem + \startitem + it's not too hard to inject experimental code + \stopitem + \startitem + so users can add their own features + \stopitem + \startitem + some day there may be alternative handlers + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={math}] + +\startsubject[title={format}] + + the opentype math specification stays close to \TeX, but has extensions and + more control (see articles & presentations by Ulrik Vieth) + +\stopsubject + +\startsubject[title={loading}] + + \startitemize + \startitem + maps more or less directly onto internal structures + \stopitem + \startitem + in \ConTeXt\ we use(d) virtual unicode fonts awaiting lm/gyre + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={processing}] + + character mapping and special element handling remains macro package + dependent + +\stopsubject + +\startsubject[title={construction}] + + \startitemize + \startitem + we split code paths when needed: traditional or opentype (no longer + heuristics) + \stopitem + \startitem + the \luaTeX\ engine provides much control over spacing and a bit more + over rendering + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={the basics of loading}] + +\startsubject[title={the format}] + + \startitemize + \startitem + it evolved out of competing formats by apple, microsoft and adobe + \stopitem + \startitem + two flavours can normally be recognized by suffix: \type {ttf} and + \type {otf} + \stopitem + \startitem + main differences are bounding box info, global kern tables, cubic vs + quadratic curves + \stopitem + \startitem + multiple sub fonts inside \type {ttc} files (font collections) + \stopitem + \startitem + it's considered a standard (so it should be possible to implement) + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={the specification}] + + \startitemize + \startitem + the only useable reference is on the microsoft website + \stopitem + \startitem + (the iso mpeg standard is more or less a bunch of ugly rendered + webpages) + \stopitem + \startitem + trial and error helps understanding/identifying fuzzy aspects + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={the available loaders}] + +\startsubject[title={the fontforge loader}] + + \startitemize + \startitem + offers the same view on the font as the editor (good for debugging) + \stopitem + \startitem + in order to process a font some optimal data structures are created + after loading + \stopitem + \startitem + we cache fonts because loading and creating these structures takes + time and it saves memory too + \stopitem + \startitem + fontforge has a lot of heuristics (catching issues collected over + time) but these are hard to get rid of when they're wrong + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={the lua loader}] + + \startitemize + \startitem + this started out as experiment for loading outlines in \MetaFun + \stopitem + \startitem + it avoids the conversion to optimal structures for handling + \stopitem + \startitem + we can hook in better heuristics (data is more raw) + \stopitem + \startitem + it fits in the wish for maximum flexibility (next stage \ConTeXt) + \stopitem + \startitem + it's rather trivial to extend and adapt without hard coding + \stopitem + \startitem + the performance can be a bit less on initial loading (pre|-|cache) + but there is a bit of room to improve + \stopitem + \startitem + it's much more efficient in identifying fonts (not a real issue in + practice) + \stopitem + \startitem + in practice most fonts behave ok (no recovery needed) but there are + some sloppy fonts around + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={what do we load}] + +\startsubject[title={tables}] + + \startitemize + \startitem + opentype is mostly tables with lots of subtables + \stopitem + \startitem + there are required, truetype outline, postscript outline, (svg and + bitmap), typography & additional ones + \stopitem + \startitem + the typographic tables specify transformations to apply (gdef, gsub, + gpos) + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={calculations}] + + \startitemize + \startitem + as we need ht/dp we need to calculate the boundingbox of postscript + outlines (cff parser) + \stopitem + \startitem + internally we use unicodes instead of indices + \stopitem + \startitem + we need to identify/filter the right unicode information + \stopitem + \startitem + we want to do more so we need to carry around more info (tounicode etc) + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={pitfalls}] + + \startitemize + \startitem + there is no real consistent approach to use of basic features: + single, one to multiple, multiple to one & many to many replacements, + and look ahead and/or back based solutions + \stopitem + \startitem + in principle consistent families like lm/gyre could share common data + and logic but otherwise there is much diversity around + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={a few details}] + +\startsubject[title={loading}] + + \startitemize + \startitem + load the file (subfont if needed) in a \Lua\ friendly format + \stopitem + \startitem + prepare for later processing and/or access + \stopitem + \startitem + optimize data structures + \stopitem + \startitem + cache the instance (and compile to bytecode) + \stopitem + \startitem + share loaded font data where possible + \stopitem + \startitem + initialize & mark enabled features + \stopitem + \startitem + pass metrics, parameters and some properties to \TeX + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={processing}] + + \startitemize + \startitem + we need to run over enabled features (also virtual non|-|opentype + ones) + \stopitem + \startitem + we use lookup hashes to determine if action is needed + \stopitem + \startitem + if needed we access detailed data and apply it + \stopitem + \startitem + there can be a few but also many hundreds of loops over the node list + \stopitem + \startitem + contextual matching can make us end up with a real lot of access and + analysis + \stopitem + \startitem + descending into discretionaries adds significant overhead (so it's + optimized) + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={traditional fonts}] + +\startsubject[title={tfm}] + + \startitemize + \startitem + there is a built|-|in loader for \type {tfm}, \type {ofm}, \type {vf} + and \type {ovf} files + \stopitem + \startitem + encoding and filename mapping is as usual (\type {enc} and \type + {map} files) + \stopitem + \startitem + (in the early days \ConTeXt\ filtered info from those \type {enc} + files too) + \stopitem + \stopitemize + +\stopsubject + +\startsubject[title={type one}] + + \startitemize + \startitem + type one fonts have their own loader that gets information from \type + {afm} files + \stopitem + \startitem + the \type {pfb} file is consulted to get the index (to unicode) + mapping + \stopitem + \startitem + the \type {afm} loader was already written in \Lua\ but we now can also use + \Lua\ for the \type {pfb} file + \stopitem + \stopitemize + +\stopsubject + +\stoptitle + +\starttitle[title={remarks}] + + \startitemize + \startitem + features like additional character kerning don't belong in the font + handler as they are (to some extent) macro package dependant + \stopitem + \startitem + the same is true for italic correction (often input related and + therefore a macro package specific issue) + \stopitem + \startitem + setting up protrusion and expansion is again somewhat macro package + dependent + \stopitem + \startitem + \ConTeXt\ has many extra font related mechanisms and features + (described in a more technical manual) + \stopitem + \blank + \startitem + this has to work well with the core subsystems: languages especially + hyphenators, specific script demands, typesetting (all kind), builders + (paragraph, page), etc. + \stopitem + \startitem + a complication is that we do this more and more in \Lua, but still need to + support the built|-|in mechanismsm too + \stopitem + \blank + \startitem + the interfacing to macro packages differs (for plain \TeX\ we use + code that ships with \ConTeXt) + \stopitem + \startitem + for bugs and issues of with fonts in \ConTeXt\ you use its mailing list (or + mail me) + \stopitem + \startitem + the \LaTeX\ interface is handled by Philipp Gesang + \stopitemize + +\stoptitle + +\starttitle[title={future}] + + \startitemize + \startitem + we'll improve handling of border cases (within the constraints of + performance) + \stopitem + \startitem + we might provide a few more hooks for plug|-|ins + \stopitem + \startitem + the type one \type {pfb} reader will be extended to provide outlines + (not complex, needed for \MetaFun) + \stopitem + \startitem + we keep playing with extra new features and virtual fonts + \stopitem + \blank + \startitem + maybe some more code can be made generic (fwiw) + \stopitem + \stopitemize + +\stoptitle + +\starttitle[title={credits}] + + \startitemize + \startitem + Kai Eigner and Ivo Geradts for (experimental) patches in the handlers + for rare, complex & creepy fonts + \stopitem + \startitem + Philipp Gesang for binding the generic code to \LaTeX\ font mechanims. + \stopitem + \startitem + Idris Samawi Hamid for testing and providing the very complex and + demanding Husayni font + \stopitem + \startitem + Hartmut Henkel for the initial cleaning up of expansion and protrusion + \stopitem + \startitem + Taco Hoekwater for the original loader and discussions and a lot more + \stopitem + \startitem + Boguslaw Jackowski and friends for the fonts and patience with us + \stopitem + \startitem + Dohyun Kim for testing and suggestions on CJK font support + \stopitem + \startitem + Mojca Miklavec for distributions, managing us, and basically everything + \stopitem + \startitem + Luigi Scarso for patiently testing and managing my patches and testing + very beta code + \stopitem + \startitem + Thomas Schmitz for using betas in deadline critital book production + and making sure we patch fast + \stopitem + \startitem + Ton Otten for permitting me to work on all this \TeX\ related stuff for + ever and ever (and using to the extreme) + \stopitem + \startitem + Wolfgang Schuster for knowing and testing every detail of \ConTeXt\ + and writing selectfont (for system fonts) + \stopitem + \blank + \startitem + and all (\ConTeXt) users who patiently accept betas and testing + \stopitem + \stopitemize + +\stoptitle + +\stopdocument diff --git a/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.pdf b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.pdf Binary files differnew file mode 100644 index 00000000000..1d93243f042 --- /dev/null +++ b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.pdf diff --git a/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.tex b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.tex new file mode 100644 index 00000000000..7d958d9076c --- /dev/null +++ b/Master/texmf-dist/doc/context/presentations/bachotex/2016/bachotex-2016-toolbox.tex @@ -0,0 +1,212 @@ +\usemodule[present-phone] + +\startdocument + +\startstandardmakeup[bottom=,top=] + + \raggedcenter + + \vfil\vfil + \dontleavehmode\scale[height=2ex]{\ssbf Grandpa's toolbox} + \vfil + \dontleavehmode\scale[height=1ex]{\ssbf (making closets)} + \vfil + \dontleavehmode\scale[height=2ex]{\ssbf Dad's hobby} + \vfil + \dontleavehmode\scale[height=1ex]{\ssbf (cleaning closets)} + \vfil + \dontleavehmode\scale[height=2ex]{\ssbf Uncle's friends} + \vfil + \dontleavehmode\scale[height=1ex]{\ssbf (talking closets)} + \vfil + \vfil + \dontleavehmode\scale[width=0.45\textwidth]{\ssbf bacho\TeX\ 2016} + \vfil\vfil\vfil\vfil + +\stopstandardmakeup + +% walk in front +% use my personal phone + +\startsection[title={closets}] + \startitemize + \startitem there's closets and closets \stopitem + \startitem take the ones you put stuff in ... e.g.\ that you buy at ikea \stopitem + \startitem you have to assemble them so you get out your toolbox \stopitem + \startitem this kid sits next to you wondering what that tool is \stopitem + \startitem what is natural for you to use might not be so for them \stopitem + \startitem but grandpa likes to carry over his knowledge and experiences \stopitem + \stopitemize +\stopsection + +% \startitem look at their toolbox in their garage or shed wondering \unknown \stopitem +% \startitem \unknown\ what tools their kids will keep (or even understand) \stopitem + +\startsection[title={interest}] + \startitemize + \startitem but \unknown\ kids get their information from the internet, not from you \stopitem + \startitem (they watch discovery channel or national geographic and know a lot) \stopitem + \startitem or they look at vloggers (no bloggers) trying to learn something \stopitem + \startitem and they keep moving on \unknown\ and on \stopitem + \startitem do gp's live long tools really make sense to them? \stopitem + \stopitemize +\stopsection + +\startsection[title={grandpas}] + \startitemize + \startitem grandpa also has a vlogger, he is called knuth \stopitem + \startitem gp is as locked into tex as the kids are into apps \stopitem + \startitem he's a do-it-him-self kind of person \stopitem + \startitem will his grandkids love watching him crafting \stopitem + \startitem and hear his stories about meetings and journals \stopitem + \stopitemize +\stopsection + +\startsection[title={writing}] + \startitemize + \startitem will future generations still putting things on paper \stopitem + \startitem just watch how handwriting evolves \stopitem + \startitem compare todays scribbles to your grandmothers letters \stopitem + \startitem the possibility of reuse doesn't even ring a bell \stopitem + \startitem after all, why should they keep that text \stopitem + \startitem eventually they will de-facebook, un-twitter and no-app \stopitem + \startitem and who cares what get lost (most eventually gets lost anyway) \stopitem + \stopitemize +\stopsection + +\startsection[title={quality}] + \startitemize + \startitem say you help someone out with some graphic work \stopitem + \startitem you send them an example \stopitem + \startitem and then get remarks based on previewing on a phone \stopitem + \startitem possibly with a broken screen \stopitem + \startitem of a fuzzy backlight \stopitem + \startitem or some blue|-|filtering going on \stopitem + \startitem no color profiled monitors needed \stopitem + \stopitemize +\stopsection + +\startsection[title={low impact}] + \startitemize + \startitem going to a meeting with you is no problem \stopitem + \startitem they are even willing to attend workshops \stopitem + \startitem the impressions they get are great, but what was it about? \stopitem + \startitem oh, that backslash (slanted thingie), they might recognize that (and never need it) \stopitem + \startitem fonts, languages, clever solutions, beautiful macros \unknown\ what impresses us + leaves no dent \stopitem + % \startitem it all sounds polish to them \stopitem + \startitem and let's face it: topics get weirder (much has been told by now) \stopitem + \stopitemize +\stopsection + +\startsection[title={devices}] + \startitemize + \startitem phones, phablets and tables .. retinal project some day \stopitem + \startitem epub devices are accepted, probably for as long as phone battery life is bad \stopitem + \startitem quality rendering is irrelevant \stopitem + \startitem larger laptops are still popular but not for long \stopitem + \startitem so in the end ... do they need typesetting at all \stopitem + \startitem a one|-|time enforced user doesn't count \stopitem + \startitem does \quote {installed on 3 billion devices} really impress \stopitem + \stopitemize +\stopsection + +% \startsection[title={moving on}] +% \startitemize +% \startitem not real when no ads \stopitem +% \startitem why should one pay \stopitem +% \startitem how many subscriptions do you need \stopitem +% \startitem no tv, no books, no newspapers \stopitem +% \stopitemize +% \stopsection + +% \startsection[title={throw away}] +% \startitemize +% \startitem we store and trust the cloud \stopitem +% \startitem delete when space is needed \stopitem +% \startitem loose or crash, and just forget about it \stopitem +% \startitem one moves from phone to phone \stopitem +% \startitem device full, buy new, wipe old and sell or give away \stopitem +% \stopitemize +% \stopsection + +\startsection[title={future}] + \startitemize + \startitem accept your fate: what is current now, is obsolete tomorrow (take cars) \stopitem + \startitem how to determine what is stable (quality) anyway (how much stayed) \stopitem + \startitem how to locate the good in the pool of mediocre \stopitem + \startitem how to be able to use your live long tools at work \stopitem + \startitem just in a few generations: scratches, chisseling, scribes, monks, gutenberg, tex, ... \stopitem + \startitem the longer we live, the more old fashioned we'll look: we live on islands of technology \stopitem + \stopitemize +\stopsection + +\startsection[title={history cycles}] + \startitemize + \startitem there id this historic cycle (reinvent the wheel) \stopitem + \startitem for instance we currently see a revival of vinyl \stopitem + \startitem is this a side effect of crappy mp3 and/or poor digital equipment? \stopitem + \startitem does it mean that eventually paper books will florish again too? \stopitem + \startitem and that old fashioned rendering and printing will return? \stopitem + \stopitemize +\stopsection + +\startsection[title={consider the following}] + \startitemize + \startitem will superintelligence really show up soon and make all our efforts futile \stopitem + \startitem maybe moderate artificial intelligence is already a killer \stopitem + \startitem scifi books seldom mention reading books \stopitem + \startitem let alone high quality typeset books \stopitem + \startitem we have an experimental hive|-|mind outside the canteen here that we're learning to typeset a paragraph\stopitem + \stopitemize +\stopsection + +\startsection[title={think of this 1}] + \startitemize + \startitem there is something called context \stopitem + \startitem say that we want to make it popular \stopitem + \startitem we make it into an phone app \stopitem + \startitem that sits in its own namespace \stopitem + \startitem but wants access to all your document \stopitem + \startitem and your adressbook, so that we can tell your friends \stopitem + \startitem it is free for personal use \stopitem + \startitem but mixed with advertisements \stopitem + \startitem and it predicts your favourite look and feel \stopitem + \startitem of course it collects your data (for your benefit) \stopitem + \startitem it organizes your content the way it thinks best \stopitem + \startitem and offers you only all kind of benefits \stopitem + \startitem and it keep buzzing and popping up \stopitem + \startitem this is what kids find normal \stopitem + \startitem and discard at a daily basis \stopitem + \stopitemize +\stopsection + +\startsection[title={think of this 2}] + \startitemize + \startitem or we can take the business view (for the old folks) \stopitem + \startitem let's call it context professional or enterprise \stopitem + \startitem subscription (only affordable for large companies, no simple plans) \stopitem + \startitem support is charged per cpu / core \stopitem + \startitem forget about the small, go 5 digit numbers \stopitem + \startitem configurations happen via the cloud (only) \stopitem + \startitem we use open source but don't tell that \stopitem + \startitem we make sure we use a many page license, we share because we ... \stopitem + \startitem we then need investors ... going big is a \quote {must} \stopitem + \startitem so eventually we sell ourselves \stopitem + \startitem naturally we get sold over and over again \stopitem + \startitem and then quit and start new \stopitem + \startitem and expect sympathy from users in the process \stopitem + \stopitemize +\stopsection + +\startsection[title={so \unknown\ grandpa}] + \startitemize + \startitem do we really want that kind of adapting \stopitem + \startitem do we really expect next generations to take over \stopitem + \startitem maybe we should keep tex in our closet \stopitem + \startitem you don't want it to become a dirty (highway) closet, does you? \stopitem + \startitem think different, think like kids (jc example) \stopitem + \stopitemize +\stopsection + +\stopdocument |