December 2012 - ntg-context - NTG Mailing Lists

different interlinear space for quotation?
by Pablo Rodríguez 09 Dec '12

09 Dec '12

Hi there, I have a text in which I want the interlinear space in narrower environments and the font size to be smaller. I tried something like the sample below, but it doesn't work (no suprise :-(). \startsetups[setups:narrow] \setupinterlinespace[line=2.8ex] \tfx \stopsetups \definenarrower[narrowlines][left=4em, setups=setups:narrow] \definelines[narrow][before={\blank\startnarrowlines[left]},after=\stopnarrowlines\blank] \stopsetups \starttext \input ward\par \startnarrow \input knuth\par \stopnarrow \input ward\par \stoptext Does anyone know how can I achieve a smaller font size and interlinear space only in narrower environments? Many thanks for your help, Pablo -- http://www.ousia.tk

2 1

different vertical space with \definelines and \setuplines
by Pablo Rodríguez 09 Dec '12

09 Dec '12

Hi Hans, I have the following sample: \definelines[narrow][before=\blank,after=\blank] \stopsetups \starttext This is a paragraph.\par \startnarrow this is a verse this is a verse \stopnarrow This is paragraph.\par \stoptext If I replace \definelines with \setuplines, before and after aren't honored. \definelines adds an extra paragraph separation space within the lines that isn't inserted with \setuplines. Is this intended? Many thanks for your help, Pablo -- http://www.ousia.tk

2 1

Re: [NTG-context] setuphead command changes?
by reviczky＠caesar.elte.hu 09 Dec '12

09 Dec '12

> Am 09.12.2012 um 02:35 schrieb reviczky(a)caesar.elte.hu: > > > Hi, > > > > The following minimal example works on live.contextgarden.net but > with the latest beta the command parameter doesn't seem work (the > "TEST" does not appear in the margin). > > > > \showframe > > \starttext > > \define[2]\cmd{\inmargin{TEST}} > > \startsubject[title=Title,command=\cmd] > > \input knuth > > \stopsubject > > \stoptext > > > > Can someone confirm this? > > > You have to use “alternative=command” before you can > apply a command: > > \define[2]\SubjectCommand > {\inmargin{TEST}} > > \setuphead > [subject] > [alternative=command, > command=\SubjectCommand] > > \showframe > > \starttext > \startsubject[title=Title] > \input knuth > \stopsubject > \stoptext Thanks. I only apply commands for certain headings, so is there a way to have that working within the startsubject or is it not inheriting from setupheads? \define[2]\SubjectCommand {\inmargin{TEST}} \showframe \starttext \startsubject[title=Intro] \input knuth \stopsubject \startsubject[title=Title,alternative=command,command=\SubjectCommand] \input knuth \stopsubject \stoptext This still doesn't show me the margin-text, whereas your example is fine. > When you want more control about the layout of your header use > \defineheadalternative to create it: > > \defineheadalternative > [Subject] > [alternative=horizontal, > renderingsetup=Subject] > > \startsetups[Subject] > \headsetupspacing > \inmargin{TEST} > \stopsetups > > \setuphead > [subject] > [alternative=Subject, > distance=0pt] > > \showframe > > \starttext > \startsubject[title=Title]% > \input knuth > \stopsubject > \stoptext That is great, thanks! Adam

2 2

[luatex-plain] call to undefined function in font-def.lua
by Philipp Gesang 09 Dec '12

09 Dec '12

Hi Hans, the plain format from context calls a non-existing function fonts.goodies.filenames.resolve(). It appears that the format was not updated to include the expected code from fonts-gds.lua. [1] Terminal output below. Regard Philipp [1] The code was introduced to font-def.lua on November 16: http://repo.or.cz/w/context.git/commitdiff/4f08d2072378de7bac2c7992876b8f70… $ luatex -fmt luatex-plain.fmt This is LuaTeX, Version beta-0.70.1-2011051923 (rev 4277) \write18 enabled. **\relax (./luatex-basics.tex) (./luatex-fonts.tex <push namespace> <./luatex-fonts-merg ed.lua>(using cache: /home/laokoon/context/tex/texmf-cache/luatex-cache/generic ) ! LuaTeX error ./luatex-fonts-merged.lua:12701: attempt to index local 'fontgoo dies' (a nil value) stack traceback: ./luatex-fonts-merged.lua:12701: in main chunk [C]: in function 'dofile' ./luatex-fonts.lua:107: in function 'loadmodule' ./luatex-fonts.lua:111: in main chunk [C]: in function 'dofile' <\directlua >:1: in main chunk. l.136 } ? ! Emergency stop. l.136 } ! ==> Fatal error occurred, no output PDF file produced! Transcript written on luatex-basics.log.

2 1

setuphead command changes?
by reviczky＠caesar.elte.hu 09 Dec '12

09 Dec '12

Hi, The following minimal example works on live.contextgarden.net but with the latest beta the command parameter doesn't seem work (the "TEST" does not appear in the margin). \showframe \starttext \define[2]\cmd{\inmargin{TEST}} \startsubject[title=Title,command=\cmd] \input knuth \stopsubject \stoptext Can someone confirm this? Adam

2 1

drops module (draft)
by Peter Rolf 08 Dec '12

08 Dec '12

Hi all, a first version of the 'drops'-module (MkIV only) is available at https://www.wuala.com/indiego/public/ConTeXt/drops/?key=caiCGLasLFmJ Taken from the included documentation.. [..] 'drops' is a small extension for ConTeXt, that allows you to add drop shadows to rectangular regions (so called boxshadows). A working installation of ImageMagick (IM) is required to create the shadow graphics. The supported color spaces are CMYK, RGB and Gray, the file formats are limited to PNG and JPG. [..] Read the manual for detailed information. The attached example is just a small test file for the 'rotation' parameter (a compensation for the object rotation, so that the shadow stays at the given direction). You will find other examples in the documentation and there is also a 'pile' example with the complete source. The 'presets' pdf contains the predefined setups for different shadow (or frame) types and it's source is a good starting point for your own experiments. This is a first draft, but most things work quite stable. If you want to help, test as much as possible. :-) *You need a recent version of ImageMagick for this module.* 6.7.8-2 to 6.8.0-7 (wrong version info 6.8.0-6): used here, should work 6.7.6-0 or lower: will fail due to incompatibilities 7.0.0.0 alpha: untested ('magick' is used instead of 'convert') Tested on Windows7 64bit and Debian 6.0.5-i386 (IM compiled from source) Happy TeXing! Peter

7 15

margin location in headertext
by reviczky＠caesar.elte.hu 08 Dec '12

08 Dec '12

Hi, Is it possible, without having to use layers, to specify the location of a frame inside the margin of the header relative to the headertext? Here's an example: --- \setupheadertexts[\setups{frames}][][][] \setupheadertexts[margin][\setups{marginframe}][][][] \setuppagenumbering[location=] \startsetups[frames] \framed[height=15mm,location=top]{frame at the top} \framed[location=top]{frame at the top} \stopsetups \startsetups[marginframe] %%% how to align this at the top? \framed[location=top]{frame not at the top?} %%% \stopsetups \showframe \starttext \input knuth \stoptext --- The workaround I'm currently using is to enlarge the height of the margin-frame to the highest one inside the header. --- \framed[location=top,height=15mm,align=top]{frame not at the top?} --- Adam

1 0

Cumulating Numbered Lists
by Malte Stien 07 Dec '12

07 Dec '12

Hi all, I can easily \setupitemgroup to achieve the following: 1. ... a. ... 1. ... b. ... 1. ... 2. ... 2. ... a. ... 1. ... …but I need the numbers/letters to cumulate as follows: 1. ... 1a. ... 1a1. ... 1b. ... 1b1. ... 1b2. ... 2. ... 2a. ... 2a1. ... Can that be done? Thank you, Malte.

3 4

Re: [NTG-context] (XeTeX) trouble debugging a "Missing number" error
by Lars Huttar 07 Dec '12

07 Dec '12

In response to Hans Hagen and Wolfgang Schuster's messages of Dec. 5, Just to let you know, in response to your messages, I am working a small, self-contained example that reproduces the problem. However I have been asked to focus on a different project for a few days, so ... please don't interpret my silence as "We asked him to do due diligence and he never answered." :-) Hopefully I'll be back with more, next week. Regards, Lars

1 0

Doubled annotation content
by Marco Patzer 07 Dec '12

07 Dec '12

In the following example the content of the annotation is printed twice. Bug? \usemodule [annotation] \defineannotation [myannotation] [alternative=command, command=\cmd] \def\cmd {\placeannotationcontent} \starttext \startmyannotation foo \stopmyannotation \stoptext Marco

4 8