- ntg-context - Mailing Lists

TeX syntax -- a guide?
by James Fisher 26 Feb '10

26 Feb '10

Hi, After a few days working in "do what the tutorials say" mode, I now want to understand TeX from a programmer's mindset. I have not been able just by practise to work out what the syntactic rules of TeX are, and I am hoping that there is a sensible guide to this somewhere. However, searches for things like "tex syntax" draw a blank. Some of the things I want to understand, for example, are: (1) what is the distinction between square brackets and curly brackets after a command? (2) Why are there sometimes lists of square-bracketed lists after a command, each with lists of seeming arguments inside them? (2) What exactly are the "variables" in a TeX file? (I've seen variable-like things sometimes referred to just plainly, sometimes with preceding backslashes as if they were commands/macros). (4) Why can't I end a square-bracketed section with a final square-bracket on a line of its own, as I may do in other programming languages? (5) How are things like \subsection, \subsubsection, \subsubsubsection, ... implemented? I am used to languages in which there is only a finite set of commands; why is the logic here not more like \section[level=1], \section[level=2], ... ? (6) Perhaps I'm misunderstanding things and all this isn't actually the fundamental syntax of TeX but just adhoc syntax defined by various macros doing different things -- is this the case; to what degree can macros define syntax? Obviously I don't expect answers to all these here, but can someone point me to somewhere on the 'net that could answer them? The only other possibilities I can see are buying an expensive copy of the TeXbook, etc. Thanks all, James Fisher

4 4

Re: [NTG-context] Math in MKIV - HOWTO
by Vyatcheslav Yatskovsky 26 Feb '10

26 Feb '10

Hi Mojca, After trying step 1 (vusialize the font) with Times math, I have the following error: systems : begin file math.tex at line 2 (c:/contextminimal/texmf-context/tex/context/base/font-run.mkii) color : system all is global activated ! Undefined control sequence. \doshowfont ...f \setstrut \dummy \localcolortrue \offinterlineskip \dostepw... <to be read again> \stoptext l.4 \stoptext The strange thing here is .mkii extension, while I definitely use mkiv. My script is \loadmapfile[original-youngryu-tx.map] \starttext \showfont[rtxptmr] \stoptext B.R., Vyatcheslav

1 0

context, jobnam
by R. Bastian 25 Feb '10

25 Feb '10

Hello, is there a way to get the option '--jobname= ' as in tex ? -- René Bastian www.pythoneon.org www.musiques-rb.org

2 2

\definetypeface broken?
by Yanrui Li 25 Feb '10

25 Feb '10

Hi, I found '\definetypeface' can not work with beta 2010.02.24. This is a minimal example: \starttypescript[serif][test] \definefontsynonym[Serif][name:texgyrepagella] \stoptypescript \definetypeface[myfonts][rm][serif][test][default] \setupbodyfont[myfonts] \starttext Hello world! \stoptext -- Best regards, Li Yanrui

2 1

Changing "chapter"-line layout
by Daniel Stender 25 Feb '10

25 Feb '10

Hi guys, simple question: how can the layout of the "chapter" line be modified? (changing the fontsize to what's \tfb). Thanks in advance & greetings, DS

3 3

MkII to MkIV
by Steffen Wolfrum 25 Feb '10

25 Feb '10

Hi, typesetting an old MkII written project with MkIV today gives more then 2000 "unable to resolve" warnings, like these ... !pages : flushing realpage 12, userpage 16 !backends : unable to resolve destination attribute 67 !backends : unable to resolve destination attribute 69 !backends : unable to resolve destination attribute 70 !backends : unable to resolve destination attribute 71 !backends : unable to resolve destination attribute 72 !backends : unable to resolve destination attribute 74 !pages : flushing realpage 13, userpage 17 !backends : unable to resolve destination attribute 75 !backends : unable to resolve destination attribute 76 !backends : unable to resolve destination attribute 83 !backends : unable to resolve destination attribute 80 !backends : unable to resolve destination attribute 81 !pages : flushing realpage 14, userpage 18 !backends : unable to resolve destination attribute 82 !backends : unable to resolve destination attribute 85 !backends : unable to resolve destination attribute 86 !backends : unable to resolve destination attribute 91 !backends : unable to resolve destination attribute 89 !backends : unable to resolve destination attribute 90 ... what does this mean? As that project did not even have 2000 \footnotes or \index or reference marks, what is meant? Paragraphs??? Steffen

2 1

[OT] TEX line breaking algorithm in JavaScript
by Mojca Miklavec 25 Feb '10

25 Feb '10

http://www.bramstein.com/projects/typeset/ PS: the author comes from the second nicest country in the world :)

3 4

Re: [NTG-context] [Fwd: hyphen breaking (URGENT)]
by Hans Hagen 24 Feb '10

24 Feb '10

On 23-2-2010 12:22, Steffen Wolfrum wrote: > > Am 25.10.2009 um 21:33 schrieb Hans Hagen: > >> Steffen Wolfrum wrote: >> >>>> \unprotect >>>> \def\FrozenTUO{MyFile} >>>> \def\doplacerawlist[#1][#2]% >>>> {\begingroup >>>> \dogetcommalistelement1\from#1\to\firstlistelement >>>> \dosetuplist[#1][#2]% >>>> \doifvalue{\??li\firstlistelement\c!coupling}\v!on >>>> {\startlistreferences{#1}}% >>>> \dosettoclevel\??li\firstlistelement >>>> \honorlocalfilterlevel >>>> \doutilities{listentries,#1}\FrozenTUO{#1}\relax\par >>>> \stoplistreferences{#1}% >> >> ^^^^ >> >> remove {#1} here >> >>>> \dosetlistmode >>>> \endgroup} >>>> \protect >> >> i probably added some proper push/pop here > > > > Today the code above gives an error: > > ! Undefined control sequence. > \doplacerawlist ...references {#1}}\dosettoclevel > \??li \firstlistelement \h... > \doplacelist ...ginoflist \doplacerawlist [#1][#2] > \doendoflist > <to be read again> > > > > Can you see what needs to be changed? sure, as the whole underlying mechanism of lists has changed (and now mostly happens in lua) that code makes no sense and iven if i made a (fake) \dosettoclevel it would not kick in so, you need to identify your need and then implement a mkiv solution Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

4 10

groupedcommand italic and upright (MkIV)
by Steffen Wolfrum 24 Feb '10

24 Feb '10

Hi, in MkII the slash became set upright, in MkIV it stays italic: \def\Textit{\groupedcommand\it\/} \def\Textmr{\groupedcommand\mr\/} \definetextmodediscretionary : {\prewordbreak\discretionary{\kern.05em\Textmr/}{}{\kern.05em\Textmr/}\kern.05em\prewordbreak}% ist schon Textmr = aufrecht ! \starttext test \Textit{non|:|italic} here. \stoptext What needs to be changed to get an upright slash in that italic group? Steffen

2 2

Math in MKIV - HOWTO (was: Lucida Fonts with MKIV)
by Mojca Miklavec 24 Feb '10

24 Feb '10

These basic set of rules should also apply to fourier or any other font that still needs better math support. I'm posting them on the list for future reference (for when the next volunteer pops up). On Fri, Feb 19, 2010 at 14:50, Troy Henderson wrote: > > I have followed the first set of instructions at > > http://wiki.contextgarden.net/Lucida ... > Is there an easy way to adapt the configuration file(s) for MKII to MKIV? > If this is possible but just requires a tedious process, I'm willing > to do this, but I have no clue of the steps needed. So here are some basic instructions: Step 1: check what's in the fonts ===== The file lucida.map includes the following lines: hlcda LucidaNewMath-Arrows-Demi <lbmad.pfb hlcdim LucidaNewMath-DemiItalic <lbmdi.pfb hlcdima LucidaNewMath-AltDemiItalic <lbmdo.pfb hlcdm LucidaNewMath-Demibold <lbmd.pfb hlcdy LucidaNewMath-Symbol-Demi <lbmsd.pfb hlcra LucidaNewMath-Arrows <lbma.pfb hlcrim LucidaNewMath-Italic <lbmi.pfb hlcrima LucidaNewMath-AltItalic <lbmo.pfb hlcrm LucidaNewMath-Roman <lbmr.pfb hlcrv LucidaNewMath-Extension <lbme.pfb hlcry LucidaNewMath-Symbol <lbms.pfb After short inspection you may notice that some are just bold variants, so you are basically left with only 6 files that you need to take care of: hlcrm LucidaNewMath-Roman <lbmr.pfb hlcrim LucidaNewMath-Italic <lbmi.pfb hlcrima LucidaNewMath-AltItalic <lbmo.pfb hlcrv LucidaNewMath-Extension <lbme.pfb hlcry LucidaNewMath-Symbol <lbms.pfb hlcra LucidaNewMath-Arrows <lbma.pfb You may want to visualize the content of those fonts by using: \loadmapfile[lucida.map] \starttext \showfont[hlcrm] \showfont[hlcrim] \showfont[hlcrima] \showfont[hlcrv] \showfont[hlcry] \showfont[hlcra] \stoptext Step 2: compare ===== It might be interesting to know what's in LM (so that you know what you need to modify): \starttext \showfont[rm-lmr10] \showfont[lmmi10] \showfont[lmex10] \showfont[lmsy10] \stoptext as well as seing what's in ams fonts perhaps. Now all the info that describes the content of these files is in math-tex.mkii (for MKII) and math-vfu.lua (for MKIV): mathematics.make_font ( "lmroman10-math", { { name = "lmroman10-regular.otf", features = "virtualmath", main = true }, { name = "rm-lmr10.tfm", vector = "tex-mr-missing" } , { name = "lmmi10.tfm", vector = "tex-mi", skewchar=0x7F }, { name = "lmmi10.tfm", vector = "tex-it", skewchar=0x7F }, { name = "lmsy10.tfm", vector = "tex-sy", skewchar=0x30, parameters = true } , { name = "lmex10.tfm", vector = "tex-ex", extension = true } , { name = "msam10.tfm", vector = "tex-ma" }, { name = "msbm10.tfm", vector = "tex-mb" }, -- { name = "rm-lmbx10.tfm", vector = "tex-bf" } , { name = "lmroman10-bold.otf", vector = "tex-bf" } , { name = "lmmib10.tfm", vector = "tex-bi", skewchar=0x7F } , { name = "lmsans10-regular.otf", vector = "tex-ss", optional=true }, { name = "lmmono10-regular.otf", vector = "tex-tt", optional=true }, { name = "eufm10.tfm", vector = "tex-fraktur", optional=true }, { name = "eufb10.tfm", vector = "tex-fraktur-bold", optional=true }, } ) You may want to check any tfm font mentioned here as well as any vector="..." mentioned. fonts.enc.math["tex-mi"] = { [0x1D6E4] = 0x00, -- Gamma [0x1D6E5] = 0x01, -- Delta [0x1D6E9] = 0x02, -- Theta [0x1D6F3] = 0x02, -- varTheta (not present in TeX) [0x1D6EC] = 0x03, -- Lambda [0x1D6EF] = 0x04, -- Xi [0x1D6F1] = 0x05, -- Pi There's a very precious source of information available for unicode mappings for many fonts that might be worth considering: tex4ht/ht-fonts/unicode/ Step 3: make use of available glyph information ===== 3a) You may use lucidabr.sty as a pretty reliable source of information to extract the mapping between: - glyph name (in LaTeX) - font - slot 3b) In char-def.lua there are some mappings between context commands and unicode points. If any mapping is missing, you need to add it anyway (else you won't be able to use that particular command), for all other commands you already have unicode point, so when you find "rightarrow" or some other glyph in font, you may look it up in char-def.lua to determine the unicode number. You may want to use both the comprehensive TeX symbol list as well as the Unicode Standard to help you out if there are some glyphs you don't know. Step 4: fix math-lbr ===== Step 5: complete the vectors in math-vfu.lua ===== I'm not completly sure about some aspects of bold math, but here are at least some points to start with. Step 6: test ===== Translate ams test paper and the comprehensive LaTeX symbol list to ConTeXt in order to test if all the characters work ok in all the math fonts supported by ConTeXt :) :) :) Mojca

3 5