- ntg-context - NTG Mailing Lists

\xmlstrip?
by Hans van der Meer 12 Mar '10

12 Mar '10

I encounter difficulties in stripping the leading and trailing whitespace from a node. The following does not work for me, typesetting \CAST delivers an empty result: \def\Cast#1{\def\CAST{#1}} \startxmlsetups xml:case:cast \Cast{\xmlstrip{#1}{}} \stopxmlsetups nor do variants like: \Cast{xmlstrip{#1}{*}} \Cast{xmlstrip{#1}{/}} \Cast{xmlstrip{#1}{/cast}} What does work is: \Cast{\xmlflush{#1}} How do I proceed? Hans van der Meer

2 1

Antykwa Toruńska and dashes
by Philipp Gesang 12 Mar '10

12 Mar '10

Hi again, when using Antykwa Toruńska I have problems getting dashes rights. Example: -0<---------------------------------------------------------------------------- \usetypescript[antykwa-torunska] \setupbodyfont[antykwa] \starttext asdf -- adsf\par asdf --- adsf\par asdf--asdf\par asdf---asdf\par \stoptext -0<---------------------------------------------------------------------------- In output here (MkIV as of yesterday) the double/triple dashes are not concatenated to en/em dashes. Everything works fine with latin modern, schola, bonum etc. What's wrong? Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

4 7

interlinespace confusion (MkIV)
by Steffen Wolfrum 12 Mar '10

12 Mar '10

Hi, I am totally confused by interlinespace usage in mkiv ... Please have a look at this torture test below: Setting bodytext to a tight interlinespace works by \setuplayout[grid=both]. But \chapter doesn't get right: Either you use \setuplocalinterlinespace, then you might get an extra space between the first and the second chaper line, or you use \setupinterlinespace, then the bodytext interlinespace gets disturbed. [btw: and how do I get a tight interlinespace in \chapter too?? here grid=both doesn't work ...] Could someone please help?! Steffen ----- \usetypescript[postscript] \definetypeface[postscript][rm][serif][times][default] \mainlanguage[de] \setupbodyfont[postscript,10pt]\setupinterlinespace[line=9pt] \def\MyChapter{% \switchtobodyfont[rm,13pt]\bf \setuplocalinterlinespace[line=16pt]% <- spurious space between 1. and 2. line % \setupinterlinespace[line=16pt]% <- bodytext interlinespace disturbed } \setuphead[chapter] [grid=both,style=\MyChapter] \setuplayout[grid=both] \starttext \chapter{Éç\\Éç\\Éç\\Éç} Éç\par Éç\par Éç\par Éç \stoptext

3 2

Why is the figure not centered
by Curiouslearn 12 Mar '10

12 Mar '10

Can someone please tell me why the code below does not (horizontally) center the figure? The caption is in the middle but the figure is not. Thanks. \usemodule[pgfplots] \starttext \placefigure[here][fig:demand]{Demand Curve} {\starttikzpicture \startaxis[line width=1pt, axis x line = bottom, axis y line =left, xmin=0,xmax=60, ymax=120] \addplot[mark=none] coordinates {(0,100) (50,0)}; \stopaxis \stoptikzpicture} \stoptext

2 2

[OT] Experiences in ConTeXt
by luigi scarso 12 Mar '10

12 Mar '10

Nice http://www.danielstender.com/granthinam/?p=769#respond -- luigi

1 0

simplefonts
by Michael Saunders 12 Mar '10

12 Mar '10

> Add > > \definefontfeature[default] [default] [mode=node,script=latn] > \definefontfeature[smallcaps][smallcaps][mode=node,script=latn] > > before \setmainfont. Thank you, Wolfgang, but this has no effect. -- m

2 1

Transliterator module, 2nd revision
by Philipp Gesang 12 Mar '10

12 Mar '10

Hi again, the transliteration module has been reworked following sunday's discussion on the list. The table groups now come in separate files and are loaded / created only on demand. The module now provides a \[start|stop]transliterate environment, credits for it go to Wolfgang. The most valuable suggestion came from Thomas: the former substitution functions that were using string.gsub() have been entirely replaced by LPeg, which proves to be surprisingly fast. (Under some circumstances, it is faster than not transliterating at all.) I have opened a bitbucket account in order to not to clutter the mailing list with archives. The tip revision can be found here: http://bitbucket.org/phg/transliterator/get/2fc2b5fbbd46.gz and the precompiled manual over here: http://bitbucket.org/phg/transliterator/downloads/transliterator.pdf Happy TeXing! Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

10 15

\completepublications does not create index entry
by Tom 12 Mar '10

12 Mar '10

\completepublications creates a satisfactory bibliography but doesn't create an index entry. Is there a parameter that I don't know about that makes this happen? Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey

3 5

simplefonts
by Michael Saunders 12 Mar '10

12 Mar '10

I couldn't get Context running from within TexnicCenter again, so I'm running it from a batch file. After pouring over all the mentions of typescripts here and there, I can't make sense of them. For example, I used to be able to write font definition files that would automatically shift between different design sizes depending on what font size was called for. How to do that here? Not a clue. Finally I settled on trying simplefonts. The two lines of documentation in Context Garden are: \usemodule[simplefonts] % load the module \setmainfont[Delicious] % set Delicious as main (serif) font I tried this at home: \usemodule[simplefonts] \setmainfont[garamondpremrpro] and, indeed, it loads Garamond, but normal ligatures (e.g. ffi) are broken, TeX ligatures (e.g. ---) are broken, small caps are broken, etc. It doesn't even take advantage of the superior figures for the footnote marks, which are now tiny, spindly things. The documentation that comes with the module is one line long: \simplefont[<font>][..,..=..,..] followed by a list of OpenType features. So, I tried it: \simplefont[garamondpremrpro] [features=liga] It doesn't seem to do anything. Even standard ligatures don't work. -- m

2 1

lpath question
by Hans van der Meer 11 Mar '10

11 Mar '10

In xml processing I have the following element: <abc> <xyz>contents</xyz> <xyz>contents</xyz> </abc> In the code it seems to make no diffence if I write /xyz or xyz without the / for the xyz-node. {\xmlindex{#1}{/xyz}{1}} {\xmlindex{#1}{xyz}{2}} In the reference manual I find the / used, as for example in {\xmlfirst{#1}{/caption}}. My question therefore: what exactly causes this behaviour? is it good coding practice to always use /xyz in this case? Hans van der Meer

2 1