- ntg-context - NTG Mailing Lists

mtxrun.lua:2167: stack overflow
by views63 14 Mar '10

14 Mar '10

Hi all, I use ConTeXt MkIV version: 2010.03.10 23:47 withTeXworks,it doesn't work. the error message:E:\context\tex\texmf-mswin\bin\mtxrun.lua:2167: stack overflow tools configuration: name=ConTeXt MkIV program=mtxrun arguments=--autogenerate, --script, context, $synctexoption, $fullname showPdf=true

3 3

Numbered descriptions
by Alain Delmotte 14 Mar '10

14 Mar '10

Hi! Going on with "ConTeXt an excursion". Using Windows XP, the minimals, TeXworks and *MkIV* I have a problem with the enumerated descriptions. With the following source (taken from the "Hasselt book" :-) ): ----------------------- \starttext Some text here \defineenumeration [remark] [location=top,text=Remark,inbetween=\blank,after=\blank] \remark In the early medieval times Hasselt was a place of pilgrimage. \subremark Nowadays the {\em Heilige Stede} is closed. Here some text before group 2. \remark In the early medieval times Hasselt was a place of pilgrimage. \subremark Nowadays the {\em Heilige Stede} is closed. Here some text before group 3. \remark In the early medieval times Hasselt was a place of pilgrimage. \subremark Nowadays the {\em Heilige Stede} is closed. Here some text. \stoptext ----------------------- I get the following numbering Remark 1 Remark 1.1 Remark 2.1 Remark 2.2 Remark 3.2 Remark 3.3 I would expect 1, 1.1, 2, 2.1, 3, 3.1 I f put: \setupenumerations[remark][headstyle=bold] \setupenumerations[subremark][headstyle=slanted] before group 2, I get Remark 1 Remark 1.1 Remark 1 Remark 1.1 Remark 2.1 Remark 2.2 numbering is reset starting with group 2 (I think this is normal) but still the following numbering is odd. Any explanation? Many thanks, Alain

1 0

simplefonts
by Michael Saunders 14 Mar '10

14 Mar '10

Thomas A. Schmitz: Thank you, Thomas. I've been studying this closely. > A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript [<typeface>] [<identifier>] I see! So, I'm guessing that it is this <typeface> which connects the typescripts to the font switching commands like \rm. My guess is: <typeface> switch serif \rm sans \ss mono \tt math \mm ?? \hw ?? \cg and that Context only permits these six families? > > In the typography manual, Hans says, > > "The third and fourth > > arguments to \definetypeface are pointers to already declared font > > sets; these are defined elsewhere." I think by "font set" he must > > mean a typescript like garamondprem, but I don't know where the font > > set (typescript?) "serif" is or why two font sets need to be pointed > > to. > ??? That's how I feel. The command in question was: \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default] The typography document says that the "[serif] [garamondprem]" "are pointers to already declared font sets; these are defined elsewhere." I know now that "[garamondprem]" is the "font set" in your typescript. I don't know what font set "[serif]" points to or why. > The same typography document goes on to explain the fifth > argument: > "The fifth argument to \definetypeface specifies specific font size > setups (if any), these will be covered in section ?? in the next > chapter." > This is getting scary, but I'm hoping putting "[optical]" there will > solve everything. > I don't follow. http://context.aanhet.net/svn/contextman/context-reference/en/co-typography… says: "The fifth argument to \definetypeface specifies specific font size setups (if any), these will be covered in section ?? in the next chapter." If this chapter were inserted into the manual, the next chapter would be about color and backgrounds, so, no luck searching there. But, I noticed that that fifth argument was filled by "[optical]" at the bottom of this page: http://wiki.contextgarden.net/Optical_Size so: "\definetypeface [minion-pro] [rm] [serif] [minion-pro] [optical]" > > I'm confused about how [GaramondPremUpper] and [garamondpremupper] > > seem to be getting associated with [rm] and [serif] after they were > > already associated with > > [GaramondPrem] and [garamondprem]. I don't see how, when I now use \rm, the > > machine is going to know whether I mean garamondpremupper or garamondprem. > > The rest of the file seems straightforward. > In ConTeXt, you are always within a certain bodyfont (the one defined with the \definetypeface command). A switch like \it or \rm will thus take the italic/roman from this bodyfont. Meaning: when you say \setubodyfont[GaramondPrem], it will use "normal" Garamond Premier, if you use \switchtobodyfont[GaramondPremUpper], it will use the superior numbers variant. Ahhh, okay. It wasn't intuitive to me, as a user, that a relatively small change (from, say, oldstyle to superiors) would take a much bigger switch (of the whole bodyfont) than would a relatively big change (from, say, roman to italic, which only needs a little \it). I wrote a set of font switches once (in LaTeX) that were all little digraph codes (major axis: rm, it, sl, ui; minor axis: rg, ac, sc, sw, in, su, nu, de, po, pl, to, tl + ornaments, which handles all of the variations that Adobe makes, anyway). Maybe I'll be able to reproduce it once I get this working. > > I get the error: > > !undefined control sequence > > <recently read> \usetypescript > > l.12 \usetypescript > > [GaramondPrem] > Then we will need your example - this is not normal behavior. okay: First, I put an almost exact copy of your file (with your comments commented out) in type-garamondprem.tex in C:\contextminimal\tex\texmf-local and ran luatools --generate, which seems to see the directory alright. Then I put the commands: \usetypescriptfile [type-garamondprem] \usetypescript [GaramondPremUpper] \usetypsecript [GaramondPrem] \setupbodyfont [GaramondPrem,12pt] in my preamble, with nothing else. When I try to run Context, the above error was returned. For the record, here is the exact contents of type-garamondprem.tex: %So we define a set of such features for the different font instances we want to define. %In my case, I want regular text with oldstyle figures, small caps with lining figures, and superior numerals. This goes into your typescript: \definefontfeature [myroman] [protrusion=pure,expansion=quality,script=latn,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes] \definefontfeature [mysmcp] [mode=node,script=latn,language=dflt,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes,smcp=yes] \definefontfeature [mysup] [mode=node,script=latn,onum=no,pnum=yes,sups=yes] %Next step: we set up the "normal" and smallcaps font: \starttypescript [serif] [garamondprem] \definefontsynonym [Garamond-Roman] [name:garamondpremierpro] [features=myroman] \definefontsynonym [Garamond-Bold] [name:garamondpremierprobold] [features=myroman] \definefontsynonym [Garamond-Italic] [name:garamondpremierproitalic] [features=myroman] \definefontsynonym [Garamond-Bold-Italic] [name:garamondpremierprobolditalicc] [features=myroman] \definefontsynonym [Garamond-SmallCaps] [name:garamondpremierpro] [features=mysmcp] \stoptypescript \starttypescript [serif] [garamondprem] \definefontsynonym [Serif] [Garamond-Roman] [features=myroman] \definefontsynonym [SerifItalic] [Garamond-Italic] [features=myroman] \definefontsynonym [SerifBold] [Garamond-Bold] [features=myroman] \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic] [features=myroman] \definefontsynonym [SerifCaps] [Garamond-SmallCaps] [features=mysmcp] \stoptypescript %Finally, define your first typeface: \starttypescript [GaramondPrem] \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default] \stoptypescript %Next step: defining a typeface with superior numbers for footnote references etc.: \starttypescript [serif] [garamondpremupper] \definefontsynonym [GaramondPremUpper-Roman] [name:agaramondproregular] [features=mysup] \stoptypescript \starttypescript [serif] [garamondpremupper] \definefontsynonym [Serif] [GaramondPremUpper-Roman] [features=mysup] \definefontsynonym [SerifItalic] [Serif] \definefontsynonym [SerifBold] [Serif] \definefontsynonym [SerifBoldItalic] [Serif] \definefontsynonym [SerifCaps] [Serif] \stoptypescript \starttypescript [GaramondPremUpper] \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default] \stoptypescript %Save this typescript somewhere where ConTeXt can find it and run luatools --generate. To use these in your documents, you need these lines Thank you again, this has been a huge help.

3 2

Including lua files
by Philipp Gesang 14 Mar '10

14 Mar '10

Dear Lua Gurus, what's the preferred way of including files in Lua? When trying my module on a different machine I noticed that it fails because Lua's dofile() does not extend to files in the texmf tree. Thus I attempted to include the file with context.ctxlualoadfile() but it doesn't work either. Have a relaxed weekend, Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

3 3

Re: [NTG-context] Dezimalkomma
by Wolfgang Werners-Lucchini 14 Mar '10

14 Mar '10

> > Hallo, > > > > I must do something wrong. It is not working for me: > > > > \setupmathematics[autopunctuation=yes] > > \starttext > > $0,1$ > > \stoptext > > maybe an too old version > As I wrote, I tested on the garden. This version is current enough I thinck. Wolfgang

2 1

Super- and sub-script in text mode, or, fonts in math mode
by James Fisher 14 Mar '10

14 Mar '10

Hi, A minor problem: I'm trying to place superscripted text in the text body -- things like '2^nd March'. I can't see anything like 2{\sup nd}, so my only known solution at the moment is math mode: $2^{nd}$. Despite this not being 'math', I don't really have an aversion to it. However, there's a problem with it: the superscripted text appears in italic Computer Modern. I'm using Gentium Book Basic as my body font, using XeTeX. The Gentium typeface is used perfectly everywhere, including the '2' in '2^nd', with the exception of the superscripted text. So what solutions are to hand? Is there either (1) super/sub commands in text mode, or (2) a way of fixing this in math mode? (Also, would this be a problem with ConTeXt or with XeTeX?) James Fisher

9 30

simplefonts
by Michael Saunders 13 Mar '10

13 Mar '10

Aditya Mahajan: > Have you read the chapter on typography in the new manual > http://context.aanhet.net/svn/contextman/context-reference/en/co-typography… Yes. Several times. And I took notes. ------------------------------ Hans Hagen: > > 1. What the first two arguments do. > the mode=base|node determines if we use traditional tex mechanisms > (base) or let mkiv do all work itself (node) > 2. What keys and values are available for the third, and what they mean. Thank you, but by "the first two arguments", I mean 1 and 2 of: \definefontfeature [1][2][3]. For example, in \definefontfeature[smallcaps][smallcaps][script=latn] I don't know what "[smallcaps][smallcaps]" is doing. > > 3. Once I have composed a \definefontfeature command, how do I use it > > in the text. > not in the text, only when defining fonts; although you can enable and > disable features in the running text (dynamicly) .. from the source: > % \startbuffer > % \definefontfeature[smallcaps][smallcaps][script=latn] > % \definefontfeature[oldstyle] [oldstyle] [script=latn] > % > % \definedfont[name:cambria at 15pt] > % > % Hello there {\setff{smallcaps}capped 123 \setff{oldstyle}123!} \blank > % Hello there {\addff{smallcaps}capped 123 \addff{oldstyle}123!} \blank > % Hello there {\addff{smallcaps}capped \subff{smallcaps}normal} \blank > % \stopbuffer > % > % \typebuffer \getbuffer Naturally, I don't know what any of this code means (which is why I seek a human language explanation), but I'm guessing that in \definefontfeature[oldstyle] [oldstyle] [script=latn] the first "[oldstyle]" creates a command or variable called "oldstyle", the second "[oldstyle]" relates this to something else (another command or variable, maybe a font file) which is also called "oldstyle", and the key-value pair "[script=latn]"qualifies this, selecting the only the Latin part of the second "[oldstyle]". (And, by the way, my font has Greek and Cyrillic as well---why disable oldstyle in them?) I think that leaves me with a command or variable or something called "oldstyle", which I could include in the text. My first guess would have been that it's "\oldstyle", but, later in your code snippet, I see "\setff{smallcaps}" and "\addff{smallcaps}". There's no telling what the difference is. So, I'm left guessing that \definefontfeature[oldstyle] [oldstyle] [script=latn] creates a possible argument for \setff{} and \addff{}, whatever they are. They might be the commands for font switching in the text. Since the code snippet isn't a human explanation, however, I can't tell--- I can only make wild guesses. > > 4. For example, I gathered that I needed a [default] [default] > > [...onum=yes...] to get oldstyle numerals by default, but what if I > > want to use some lining numerals here and there? > > \definefontfeature [lining] [lining] [...onum=no...] > > {\lining 123} > > doesn't do it. > lnum=yes I tried this, and \definefontfeature [lining] [lining] [lnum=yes] {\lining 123} still gives me "undefined control sequence" on \lining. I also tried {\switchtobodyfont [lining] 123}, which had no effect. > > 5. How I could use the superior and inferior shapes in my font---like > > for the footnotemarks, for example? > hm, with sups=yes,subs=yes i guess but better use \high{..} and \low{..} > as often such font features are rather limited and depend on the font I'll have to try that out (since I know which fonts have them), but: \definefontfeature [?] [?] [sups=yes,subs=yes] ? ------------------------------ Thomas A. Schmitz: > This is not to disparage Wolfgang's great simplefonts module, but I learnt setting up fonts the old-fashioned way (with typescripts), > so I will give a few explanations about this approach. Most of what you want can be achieved easily. I have Garamond Premier myself, and this is how I set it up: Thank you, this is very encouraging. I used to do this with otftotfm and .fd files, so it's not totally alien to me. I just need to grasp the syntax of the Context commands. I've been pouring over your example. There are a few points I still don't understand. ... > Next step: we set up the "normal" and smallcaps font: > \starttypescript [serif] [garamondprem] > \definefontsynonym [Garamond-Roman] [name:garamondpremierpro] [features=myroman] > \definefontsynonym [Garamond-Bold] [name:garamondpremierprobold] [features=myroman] > \definefontsynonym [Garamond-Italic] [name:garamondpremierproitalic] [features=myroman] > \definefontsynonym [Garamond-Bold-Italic] [name:garamondpremierprobolditalicc] [features=myroman] > \definefontsynonym [Garamond-SmallCaps] [name:garamondpremierpro] [features=mysmcp] > \stoptypescript > > \starttypescript [serif] [garamondprem] > \definefontsynonym [Serif] [Garamond-Roman] [features=myroman] > \definefontsynonym [SerifItalic] [Garamond-Italic] [features=myroman] > \definefontsynonym [SerifBold] [Garamond-Bold] [features=myroman] > \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic] [features=myroman] > \definefontsynonym [SerifCaps] [Garamond-SmallCaps] [features=mysmcp] > \stoptypescript I don't understand the syntax of \starttypescript. It doesn't appear in the manual. It occurs twice in the "typography" document. In both cases the first argument appears to be the name of the typescript. In one example, there is only one argument, and in the other example, the second argument appears to be a list of encodings. Since everything is now utf-8, I guess that could be forgotten. So, in your example here, I take "serif" to be the name of both typsecripts, but I don't know what [garamondprem] is doing. It's never spelled out, but from looking at examples of \definefontsynonym [1][2] in the docs, I think it means something like "what we used to call 2 we can now call 1", i.e., telling the machine to replace instances of "1" with "2". If this is the case, your third arguments above just seem to apply your features to the fonts referred to, which makes sense. I don't see, though, why this has to be done twice, and with an extra layer of misdirection. E.g., instead of: \definefontsynonym [Garamond-Roman] [name:garamondpremierpro] [features=myroman] \definefontsynonym [Serif] [Garamond-Roman] [features=myroman] why not just: \definefontsynonym [Serif] [name:garamondpremierpro] [features=myroman]? I think the purpose of the above step is to connect identifiers like "Serif" to a qualified font file. > Finally, define your first typeface: > > \starttypescript [GaramondPrem] > \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default] > \stoptypescript I think this is a typescript called GaramondPrem that contains a typeface called GaramondPrem. It seems a little redundant that they have the same name. I know that the typescripts are referred to by \usetypescript, but I don't know where typefaces are referred to, so maybe it's just a dummy argument. The "[rm]" seems to be what links this to the font switching command, and the "[garamondprem]" obviously refers to both the typescripts you defined above. I don't understand what the "[serif]" is doing. In the typography manual, Hans says, "The third and fourth arguments to \definetypeface are pointers to already declared font sets; these are defined elsewhere." I think by "font set" he must mean a typescript like garamondprem, but I don't know where the font set (typescript?) "serif" is or why two font sets need to be pointed to. The same typography document goes on to explain the fifth argument: "The fifth argument to \definetypeface specifies specific font size setups (if any), these will be covered in section ?? in the next chapter." This is getting scary, but I'm hoping putting "[optical]" there will solve everything. > Next step: defining a typeface with superior numbers for footnote references etc.: > \starttypescript [serif] [garamondpremupper] > \definefontsynonym [GaramondPremUpper-Roman] [name:agaramondproregular] [features=mysup] > \stoptypescript > \starttypescript [serif] [garamondpremupper] > \definefontsynonym [Serif] [GaramondPremUpper-Roman] [features=mysup] > \definefontsynonym [SerifItalic] [Serif] > \definefontsynonym [SerifBold] [Serif] > \definefontsynonym [SerifBoldItalic] [Serif] > \definefontsynonym [SerifCaps] [Serif] > \stoptypescript I think I follow you, up to the line: \definefontsynonym [SerifItalic] [Serif]. These last lines seem to say that if you're in bold or italic, that you should still use regular superior figures, but the font has its own bold and italic superiors. I think that's true of all the weight/shape/design size variations in the set. > \starttypescript [GaramondPremUpper] > \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default] > \stoptypescript I'm confused about how [GaramondPremUpper] and [garamondpremupper] seem to be getting associated with [rm] and [serif] after they were already associated with [GaramondPrem] and [garamondprem]. I don't see how, when I now use \rm, the machine is going to know whether I mean garamondpremupper or garamondprem. The rest of the file seems straightforward. > OK so far? Thank you---that brought me a lot closer to understanding! after saving your example and running luatools --generate, I put the last lines in my test document and tried running Context on it in the usual way. I get the error: !undefined control sequence <recently read> \usetypescript l.12 \usetypescript [GaramondPrem] > 5. How I could use the superior and inferior shapes in my font---like > for the footnotemarks, for example? > > You have defined a font instance with superiors. To use it, set up your footnotes accordingly: > > \setupfootnotes[textstyle=normal, > textcommand={\switchtobodyfont[GaramondPremUpper]}, > numbercommand={\switchtobodyfont[GaramondPremUpper]}] > 7. Maybe \definefontfeature is how I should turn on hz? > With the fontfeature, we have defined to use protrusion=pure,expansion=quality . To enable it, put this in the preamble of your document: > \enableprotruding > \enableadjusting I'll try these when I get things working. Thanks again. ------------------------------ Wolfgang Schuster: > \setupalign[hanging,hz] Or maybe I'll try that. ------------------------------ Andreas Harder: >> 5. How I could use the superior and inferior shapes in my font---like >> for the footnotemarks, for example? > \definefontfeature [sups] [default] [sups=yes] > > \setupnote > [footnote] > [command=, % -> numbercommand > textstyle=, % -> textcommand > numbercommand=\setff{sups}, % use superscript-figures > textcommand=\setff{sups}] > > So you don't have to define GaramondPremUpper. Thank you. With this, the marks in the text look good, the ones at the bottom (with the footnotes) look absurdly small. I suspect this might be because they have been optically scaled down, not switched to the smaller design size, so they seem to evaporate. They might look better if they remain the same size as in the text, I'm not sure. ------------------------------ Wolfgang Schuster: http://wiki.contextgarden.net/Optical_Size Ahhh, the rest of my weekend. Thank you. -- m

3 2

colored column
by Wolfgang Werners-Lucchini 13 Mar '10

13 Mar '10

Hallo, can someone explain how to write a table column in color, please? The following example worked in 2006 but is not working anymore: \starttext \starttable[o1|\{C{red}|] \VL red \VL\SR \stoptable \stoptext Wolfgang Schuster posted last year the following example: \NewFormatKey W#1% {\ReadFormatKeys b{\localstartcolor[#1]\{} a{\}\localstopcolor}} \starttable[o1|W{red}c|] \VL red \VL\SR \stoptable But this results in printing '{red}' in red, not 'red'! And this variant paints the following vertical line in red too: \NewFormatKey W#1% {\ReadFormatKeys b{\localstartcolor[#1]} a{\localstopcolor}} \starttable[o1|W{red}c|] \VL red \VL\SR \stoptable So, how can I do the job? Wolfgang

2 1

simplefonts
by Michael Saunders 13 Mar '10

13 Mar '10

> This works > > \definefontfeature[default] [default] [mode=node,script=latn] > \definefontfeature[smallcaps][smallcaps][mode=node,script=latn] > > \usemodule[simplefonts] > > \setmainfont[garamondpremrpro] Thank you once again. That _did_ work, after I got rid of an \os (I used it because I saw it in the manual). The command \definefontfeature intrigues me greatly. I wonder if it could solve all my problems. I'd love to understand it so that I don't end up coming in here and asking you to write all my font setups line by line. I Googled it and found only a few scattered examples here and there, mostly from this list. I wish I could find an explanation of it written down somewhere. For example, I would very much like to know: 1. What the first two arguments do. 2. What keys and values are available for the third, and what they mean. 3. Once I have composed a \definefontfeature command, how do I use it in the text. 4. For example, I gathered that I needed a [default] [default] [...onum=yes...] to get oldstyle numerals by default, but what if I want to use some lining numerals here and there? \definefontfeature [lining] [lining] [...onum=no...] {\lining 123} doesn't do it. 5. How I could use the superior and inferior shapes in my font---like for the footnotemarks, for example? 6. Could I use \definefontfeature to set up the different design sizes of my font (I'm trying to use some standard Adobe fonts like Garamond Premiere Pro, which have design sizes), as well as its other features? 7. Maybe \definefontfeature is how I should turn on hz? I'm sure these things must be possible, but I'm stumped about how to find them out. -- m

7 16

streams
by Philipp Gesang 13 Mar '10

13 Mar '10

Hello all, the streams module could help typesetting my current work but all the examples fail in mkiv. (The output from mkii is impressive, though.) The snippets I tried are from the comments of http://source.contextgarden.net/tex/context/base/m-streams.tex and another one from the wiki http://wiki.contextgarden.net/Columns#Streams Here are the ConTeXt error messages, seems that \FlushLeftAndRight is the culprit but I don't really know where to start looking because the command sequences are not legible in this truncated form. (Is there some switch that prevents ConTeXt from shortening the names at least in the log file?) -8<---------------------------------------------------------------------------- ! Undefined control sequence. \checkedfullsplitfirstmarks ...litfirstmarknumber #1\else \normalsplitfirstm... \fetchmark ...sname \??mk \??mk #3\endcsname {#1}} \fi \fi \erasemarknotes ...fetchmark [mn:#1][column:first] }\edef \lastmarknote {0\fe... \flushoutputstreams ...:\firstoutputstream :reset} \directsetup {stream:\seco... \@@ar@@1 ...lushoutputstreams [\v!left ,\v!right ] \ifvoid \outputstreamtag \... \redoloop ->\expandrecursecontent \endofloop ... l.20 \FlushLeftAndRight ? ! Emergency stop. \checkedfullsplitfirstmarks ...litfirstmarknumber #1\else \normalsplitfirstm... \fetchmark ...sname \??mk \??mk #3\endcsname {#1}} \fi \fi \erasemarknotes ...fetchmark [mn:#1][column:first] }\edef \lastmarknote {0\fe... \flushoutputstreams ...:\firstoutputstream :reset} \directsetup {stream:\seco... \@@ar@@1 ...lushoutputstreams [\v!left ,\v!right ] \ifvoid \outputstreamtag \... \redoloop ->\expandrecursecontent \endofloop ... l.20 \FlushLeftAndRight ! ==> Fatal error occurred, no output PDF file produced!MTXrun | fatal error: return code: 1 -8<---------------------------------------------------------------------------- -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

2 3