- ntg-context - Mailing Lists

page layout
by Sebastien Mengin 08 Apr '10

08 Apr '10

Hi, Say I want to typeset a 10 x 18 cm book and print proofs on a A4 paper. Margins : top = 1cm bottom = 1.5cm left & right = 1cm I'd like crop marks to. My attempts based on the docs fail. Sorry, but this simple request is not easy to deduce directly from the beginners doc -- although I translated the chapter about page layout (sigh...) Thanks in advance. -- Sébastien Mengin Édition et logiciels libres < Mise en page avec LaTeX > http://edilibre.net

7 21

Re: [NTG-context] \bigl \bigr \big problems
by Hans Hagen 08 Apr '10

08 Apr '10

On 8-4-2010 10:37, Mikael Persson wrote: > Thanks for you answer and explanation. Is there a reason why you do > not add \| to get double bars? This is the way it is done in LaTeX > (OK, not really an argument). I'm just curious. we never had \| in mkii and in mkiv it's equivalent to | (just like \$ is $ and not two $'s) .. i can find no reason for an escaped | being two |'s 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 -----------------------------------------------------------------

1 0

Re: [NTG-context] \bigl \bigr \big problems
by Mikael Persson 08 Apr '10

08 Apr '10

On Thu, Apr 8, 2010 at 10:37 AM, Mikael Persson <mickep(a)gmail.com> wrote: > On Thu, Apr 8, 2010 at 10:31 AM, Hans Hagen <pragma(a)wxs.nl> wrote: >> On 8-4-2010 7:40, Mikael Persson wrote: >> >>> Ok Hans, with the beta from yesterday the absolute values change size, >>> but there are some problems still: >>> >>> 1) The absolute value bars are not just "straight lines" when using >>> \big and friends, but som kind of line that is thicker in the middle. >>> (zoom i on attached pdf) >> >> this is because lm has no such characters so they are made from the smaller >> ones (extensible characters) >> >> in traditional lm this can go unniticed (depends a bit in the exact >> definition but in mkii you will see two stacked | just not touching but in >> mkiv we use overlap - which is custom in opentype anyway); so what you >> observe is an artefact of the viewer - it might be that future versions of >> luatex deal better with this as it relates somewhat with how things are >> dealt with in the backend but you will observe similar effects in pdftex >> >> in an earlier version i used rules but then found out that the | has round >> tops (ok, i could use pdf literals to draw lines but not today) >> >>> 2) The horizontal spacing in the \big version seems to be bigger than >>> for the \bigl/\bigr version (and similar for \Big vs \Bigl/\Bigr). I'd >>> expect the same spacing (the l and r are just there for the writer to >>> easily see what is left and what is right). >> >> repaired .. (i also added \plainbigmathmode >> >>> 3) I'd expect that \| gives double bars, like the || one get from >>> \Vert and not |. This is not so (see the attached file). Moreover, it >>> is not possible to do \bigl\Vert right now to get a bigger ||. >> >> i've added double bars so this works: >> >> $\biggl\Vert x^n\biggr\Vert$ >> $\biggl{||} x^n\biggr{||}$ >> $\biggl|\biggl| x^n\biggr|\biggr|$ >> >> there will be a new beta later today or tomorrow >> >> Hans Thanks for you answer and explanation. Is there a reason why you do not add \| to get double bars? This is the way it is done in LaTeX (OK, not really an argument). I'm just curious. Mikael

1 0

\bigl \bigr \big problems
by Mikael Persson 08 Apr '10

08 Apr '10

Dear list, I have problems with \big, \bigl, \Bigl, ... %% Example \def\foo#1{\type{#1}: #1} \starttext \foo{$|x|^n$} % as expected. \foo{$\bigl|x^n\bigr|$} % expect bigger bars \foo{$\big|x^n\big|$} % expect bigger bars \foo{$\Bigl|x^n\Bigr|$} % too small again (but bigger than \big) \foo{$\biggl|x^n\biggr|$} % too small again (but bigger than \big) \foo{$\Biggl|x^n\Biggr|$} % too small again (but bigger than \big) \foo{$\|x^n\|$} % expect two bars \foo{$\bigl\|x^n\bigr\|$} % expect two bars and bigger ones \stoptext %%% Stop example It gives the attached pdf file with latest minimals and mkiv. Mikael

2 4

Re: [NTG-context] randomize
by Wolfgang Werners-Lucchini 08 Apr '10

08 Apr '10

> > I know this and I have triggerd this by hand. So there is a lot of > > time between. I have purged files between every run and I got the > > same result if I wait 1 second, 1 minute or 1 day. > > Well, then it probably qualifies as a bug, and, since the .tuc > file > has apparently been dismissed as a cause, you'd have to provide > more > precise information if you're interested in having it corrected (or > do the debugging yourself, of course). > > Arthur I have found a discussion on this thema. See http://lua-users.org/lists/lua-l/2007-03/msg00564.html So I have changed the example to ------------------------------------------------------------- \starttext \startluacode math.randomseed(os.time()) _=math.random() \stopluacode Encode your Name and Surname as a \startluacode local a = {'null-terminated', 'dollar-terminated', 'Pascal'} context('%s string', a[math.random(1,3)]) \stopluacode \stoptext ------------------------------------------------------------- and this is working ok! Wolfgang

3 3

hyphens in verbatim text
by Hongwen Qiu 08 Apr '10

08 Apr '10

-- in verbatim text displayed as a single -, no matter in \type{} or in typing environment or something like that. current version: 2010.03.30 18:56 $ luatex --version This is LuaTeX, Version beta-0.60.0-2010040422

3 4

No indicators in registers when using french as main language
by Vianney le Clément 07 Apr '10

07 Apr '10

Hello, The subject says it all. \mainlanguage[fr] \starttext \index{Item}Item \placeindex \stoptext There is no indicator "i" in the index. It appears when you comment out the first line or change it to another language. Adding \setupregister[index][indicator=yes] does not help. Another, probably unrelated, problem is that \completeindex does not seem to do anything. Vianney

2 2

Courier font in TexLive
by Tom 07 Apr '10

07 Apr '10

The code that follows seems to work but gives me a warning: pdfTeX warning: pdftex.exe (file ec-urw-courier.map): cannot open font map file The PDF lists 3 embedded fonts: LMRoman10-Regular, LMSans10-Regular & NimbusMonL-Regu. Does NumbusMonl-Regu looks like Courier? \usetypescriptfile[type-win] \usetypescript[courier] \setupbodyfont[courier,tt,10pt] \definetypeface[TeleType][tt][mono][courier][default][encoding=ec] \usetypescriptfile[type-lucida] \setupbodyfont[lucida,ss,18pt] \definetypeface[TextFont][rm][serif][lucida][default][encoding=ec] \switchtotypeface[TextFont][12pt,rm] \starttext \input knuth \blank[big] \switchtotypeface[TeleType][tt,10pt] \input knuth \stoptext Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey

2 5

beta: pdfboxes missing
by Peter Rolf 07 Apr '10

07 Apr '10

Hi, no more trimbox and cropbox here. example is ---- \nopdfcompression \starttext\null\stoptext ---- MTXrun | current version: 2010.04.07 14:19 This is LuaTeX, Version beta-0.60.0-2010040410 (rev 3591) This is LuaTeX, Version beta-0.60.0-2010040521 (rev 3596) [minimals] best wishes, Peter

2 1

Re: [NTG-context] randomize
by Wolfgang Werners-Lucchini 07 Apr '10

07 Apr '10

> > Now it works. But WHY? > > Because that's the way random number generators works. They're > not > random at all, they generate completely predictable number > sequences > from a "seed": each time you use the same seed, you get the exact > same > sequence. In your case, you used os.time() as a seed, which is an > integral number of seconds elapsed since some fixed date, and the > fact > you saw the same number ten times simply means your code was ran > ten > times within the same second. I know this and I have triggerd this by hand. So there is a lot of time between. I have purged files between every run and I got the same result if I wait 1 second, 1 minute or 1 day. Wolfgang

2 1