- ntg-context - Mailing Lists

where \xmlnofelements
by Hans van der Meer 15 Mar '10

15 Mar '10

Here \xmlnofelements (seen in the refman) gives ! Undefined control sequence. \@@su:xml:case:processing ...fnum \xmlnofelements Has this macro disappeared? Best replacement? I would like to switch on a node having other nodes in it besides text content. Hans van der Meer ConTeXt ver: 2010.03.10 23:47 MKIV fmt: 2010.3.11 int: english/ english

1 0

German ConTeXt Initiative
by Mojca Miklavec 15 Mar '10

15 Mar '10

Hello, Two Germans suggested to start a forum in addition to the existing mailing list. Even though it might be a problem to get enough active people to participate, I see no reason for not enabling the forum on the garden as opposed to using some arbitrary web page. Any thoughts, ideas and comments about selection of software for running a forum are welcome. (I was also thinking about HyperNews which is a forum with "mailing list interface".) Mojca On Sat, Mar 13, 2010 at 20:41, Hannes Riebl wrote: > Hi Mojca, > > my name is Hannes. I've set up the german ConTeXt board on > http://context.pytalhost.de/. > > Yasser asked me to contact you because of our idea to start a german > community platform for ConTeXt. > > We both prefer a board instead of a mailing list because we think it's > easier to use especially for unexperienced users. Another reason is that I'm > not very experienced with mailing lists and have never set up one neither do > I know HyperNews. I personally like PunBB because it's lightwight and easy > to set up and administer. > > In order to have a centralized ConTeXt community you proposed to run the > board on contextgarden.net. I think that's a good idea. Would you provide a > subdomain? Could the board be installed on the same server on which the wiki > running on? At the moment it is running on a free webspace. Therefore we > have ads on the site. > > Waiting for your answer. =) > > Regards, > Hannes ... > We will not get any users for ConTeXt when there is no knowledge in germany. > And some good examples of documents createt with context. > > Our plan is more to write a german book on ConTeXt. Not a reference manual > (who are we to write it) but a step by step instruction how to write a > thesis. Academia and thesises is the main task to be targeted, so want to > write the according book. > > We want to organize it in this forum. To get users will be easy when we can > (I repeat myself here) get a link to the forum in the wikipedia article. I > hope that the responsible admins will include it. > > I hope you got what I meant.

5 6

simplefonts
by Michael Saunders 15 Mar '10

15 Mar '10

Thomas A. Schmitz: > That may be a lack of imagination on your part. If you want something that follows LaTeX rules, it might be a good idea to use LaTeX. It would have been a good idea to say so from the start instead of wasting my time. I'm going to try to go on using Context without wasting any more of your time. First, I have to figure out why your typescript gives me Latin Modern. -- m

1 0

What do you miss in ConTeXt?
by Wolfgang Schuster 15 Mar '10

15 Mar '10

Hi all, ConTeXt has many features but sometimes there is something missing, what feature or package do you miss which is already available in another TeX system or unavailable in any TeX system? Wolfgang

26 88

Re: [NTG-context] ntg-context Digest, Vol 69, Issue 77
by Michael Saunders 14 Mar '10

14 Mar '10

Henning Hraban Ramm: >> \usetypsecript [GaramondPrem] > > Here's a typo. Yes, that was it, thank you. Now when I run it it gives me... ... Latin Modern. > ------------------------------ Hans Hagen: >> My guess is: >> <typeface> switch >> serif \rm >> sans \ss >> mono \tt >> math \mm >> ?? \hw >> ?? \cg >> and that Context only permits these six families? > > it can support as many as you want but only a few make sense If you say so! > you can combine such combinations in typefaces and mix then any way and > use multiple such mixtures in one document I'm sure it's easy if you know how. I'm just trying to find out how. >> (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. > > sounds complex .. It's very easy to use, and it allows me to access any feature of my fonts with a digraph switch. Also, it keeps the different kinds of shapes on independent axes, so I can say: \it 123 \in 456 \bd 238 \rm 909 to get the numbers set in: italic; italic inferiors; bold italic inferiors; bold roman inferiors, because I also have the weight and width on separate axes. I can't imagine anything simpler to use. > it's more like: > > [typefaceone|typefacetwo|...| [rm|ss|tt|..] [tf|it|..] That looks like a much more complicated font switch. What command are those arguments to? > so if you want a smallcaps set, you'd best do something > > \definetypeface[Whatever] [....] > \definetypeface[WhateverSmallcaps][....] > > and then switch the lot to smallcaps using a typeface switch (which is > quite fast) instead of defining all kind of extra smallcaps instances > within the main typeface You are saying that putting: \definetypeface[WhateverSmallcaps] [undocumented argument] [undocumented argument] [some other typescript somewhere] in one file and then invoking it in another with (I think maybe?): \usetypescript[that other typescript from somewhere] \usebodyfont[WhateverSmallcaps] is easier than saying: \sc ?

3 2

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