- ntg-context - Mailing Lists

Re: [NTG-context] Removing Introduction section number
by Vyatcheslav Yatskovsky 07 Jun '10

07 Jun '10

> There are two cases: > 1. You want Introduction in the table of contents. Then you should copy > section to another head, and setup it with number=no (have no time to test): > > \definehead[secnonum][section] > \setuphead[secnonum][number=no] > \secnonum{Introduction} > > 2. You don't want Intruduction in the table of contents. Then just use > \subject{Introduction}. Thank you too! I do want Introduction to be in the contents! Maybe, its easier to setup \subject so that it will be included, then to invent new keywords? -- Best Regards, Vyatcheslav Yatskovsky

1 0

Lua in LuaLaTeX is diferent??
by Jaroslav Hajtmar 06 Jun '10

06 Jun '10

Hi, I did a Lua application for ConTeXt, and now I wanted to adapt it to work even LuaLaTeX. On what needs to be careful? Compiling by LuaLaTeX specific messages appear as if the Lua in LuaLaTeX didnt know some Lua commands (i.e. split, find .... ). On what needs to be careful generaly when programming applications for LuaLaTeX? Thanx Jaroslav

3 9

updating context don´t work anymore on mac os x snow leopard
by Bernhard Rosensteiner 06 Jun '10

06 Jun '10

Hi all, today i tried to update context and also updated first-setup.sh and now i get in terminal: Bernhards-MacBook-Pro:ConTeXt Bernhard$ rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh . receiving file list ... done sent 37 bytes received 91 bytes 256.00 bytes/sec total size is 3573 speedup is 27.91 Bernhards-MacBook-Pro:ConTeXt Bernhard$ . /Applications/ConTeXt/first-setup.sh receiving file list ... done sent 37 bytes received 132 bytes 112.67 bytes/sec total size is 5363753 speedup is 31738.18 /Applications/ConTeXt/bin/mtxrun:1932: bad argument #1 to 'osgetenv' (string expected, got boolean) When you want to use context, you need to initialize the tree by typing: . /Applications/ConTeXt/tex/setuptex in your shell or add "/Applications/ConTeXt/tex/texmf-osx-64/bin" to PATH variable if you want to set it permanently. This can usually be done in .bashrc, .bash_profile (or whatever file is used to initialize your shell). i don´t know where the problem lies (obviously mtxrun is complaining). the last update i did worked normal (ConTeXt ver: 2010.05.24 13:05 MKIV fmt: 2010.6.1) Please help! best regards Bernhard

5 9

dodosetreference undefined
by Yury G. Kudryashov 06 Jun '10

06 Jun '10

Hi! \dodosetreference is not defined, but \dododosetreference is defined twice in strc-ref.mkiv. This breaks \pagereference, hence t-fixme. I think that the first definition should be replaced with \def\dodosetreference.

3 3

Re: [NTG-context] 3. Re: \MPpos, pxy, initialize_box(), oh, my! (Hongwen Qiu)
by Adam Fuller 06 Jun '10

06 Jun '10

hmm, that's interesting. the source of the metafun manual is a logical place to look... hadn't thought of that, but where can i find it? i searched the source browser for metafun and metafun.tex to no avail. the challenge of learning a new system like context is like cooking out of someone else's kitchen: everything you need is probably there somewhere, it's just a matter of knowing where to look. yes, i'd like to know how this family of macros---\fpos, \tpos, mpos:box and mpos:par and friends, etc.---work, and what information you can get from them. the only mention of these on this mailing list seems to be that bunch of messages you forwarded, which was back in 2008. if i can get a bit of a kickstart toward figuring them out, i'd be compelled to put the basics in the wiki. assuming mpos:box and mpos:par were some sort of built-in MPgraphics, i compiled the following short context document, where mpos:box and mpos:par had no effect :( \setupMPvariables[mpos:box][linecolor=darkred] \setupMPvariables[mpos:par][linecolor=darkred] \startpositionoverlay{testing_paragraph_outline} \setMPpositiongraphic{pos1}{mpos:box}{self=pos1} \setMPpositiongraphic{pos1}{mpos:par}{self=pos1} \stoppositionoverlay \defineoverlay[mylayer][\positionoverlay{testing_paragraph_outline}] \setupbackgrounds[page][background=mylayer] \starttext \fpos{pos1}Something special.\tpos{pos1} \stoptext On 6/06/2010 12:34 a.m., ntg-context-request(a)ntg.nl wrote: > Date: Sat, 05 Jun 2010 19:12:28 +0800 > From: Hongwen Qiu<qiuhongwen(a)gmail.com> > To:ntg-context@ntg.nl > Subject: Re: [NTG-context] 3. Re: \MPpos, pxy, initialize_box(), oh > my! (Hongwen Qiu) > Message-ID:<4C0A311C.6010808(a)gmail.com> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > ? 2010?06?05? 10:56, Adam Fuller ??: >> > my initial post had a mistake: i meant to refer to the/Metafun/ >> > manual, not the Metapost manual. that probably didn't help. > Actually, I know that you mean the/Metafun/ manual. >> > i guess what i should have said is, i know that pxy can give me the >> > bounding/box/ (the rectangle with the maximum horizontal and vertical >> > extents of its contents, be they set in horizontal or vertical mode), >> > but can it give me the subset of that, the bounding/path/, if you >> > will, when the contents are text which flows over several lines. the >> > bounding/path/ may not be rectangular, although it will be something >> > like the union of the bounding boxes of the text's individual lines. > So now, I understand what mean. >> > i think if you look at the correct reference, the difference of the >> > effects is clear. i think the challenge is that you don't know where >> > the line breaks will occur until you typeset it. --adam > And the source code from the manual may help you: > > \setupMPvariables[mpos:box][linecolor=darkred] > \setupMPvariables[mpos:par][linecolor=darkred] > > \startpositionoverlay{backgraphics} > \setMPpositiongraphic{A-3}{mpos:box}{self=A-3} > \setMPpositiongraphic{A-4}{mpos:box}{self=A-4} > \setMPpositiongraphic{b:A-5}{mpos:par}{self=A-5} > \setMPpositiongraphic{b:A-6}{mpos:par}{self=A-6} > \stoppositionoverlay > > \fpos {A-5} Because the text must be laid on top of > the graphic, the graphic must precede the first word in the > typeset stream or it must be positioned on a separate layer. > In the latter case it can be calculated directly after the > paragraph is typeset, but in the former case a second pass > is needed. \tpos {A-5} > > Given the above code, I think you can get some information about the > horizontal and vertical pos of texts from \fpos and \tpos. And the > mpos:par is defined in anch-pgr.mkii and anch-pgr.mkiv. But I haven't > dig into the code which implement mpos:par. Hope you can find useful > information there. > > And hope the following message I just searched out will help you too: > > http://archive.contextgarden.net/message/20080107.024554.314d9fee.ca.html >

2 1

ConTeXt unit testing
by Yury G. Kudryashov 06 Jun '10

06 Jun '10

Hi! Are there any automatic unit test for ConTeXt distribution? At least the bug with referenceformat can be catched using something like context test pdftotext test.pdf test.txt diff test.txt test.txt-good And the bug with broken footnote can be catched using just "context test". If there are unit test, where can I find them (I'd like to add more)? If there are no, any objections against adding them, and testing before releasing new beta?

6 13

\reference fails in the new beta
by Michael Saunders 06 Jun '10

06 Jun '10

\starttext \reference[test]{test} \stoptext Has the syntax of \reference changed?

2 1

Re: [NTG-context] Wrong spacing before and after commas in math(?)
by Warrence 05 Jun '10

05 Jun '10

On Fri, 4 Jun 2010, "Aditya Mahajan" wrote: > Does > > \setupmathematics[autopunctuation=no] % or yes > > give better result? (Are you using MKIV or MKII)? > > Aditya \setupmathematics[autopunctuation=no] seems to fix the spaces before the x, but "...," is still bit ugly. I'm using MkIV, sorry for not mentioning it. > the default setup is for coordinates > > eventually we will have layer that implements settings for specific > fields as each demand their own rules (same for symbols) > > Hans Do you mean coordinates like "a vector (x,y,z)"? I still think that the extra space before "y" and "z" would be appreciated. But nevertheless, different settings for different needs sounds like a good idea. Thank you, Stefan.

1 0

new beta
by Hans Hagen 05 Jun '10

05 Jun '10

Hi, I uploaded a new beta to the website (will be synced with the garden minimals). I'm in the process of removing old code that is no longer needed (after all, luatex evolves). As part of the process there has been some changes in the generation of the format. It works ok on my machine (windows 7) and Taco's (linux). It might be that some things are broken but I see no immediate problems. Keep in mind that as we're now in beta mode again, we also need luatex > 0.60 and we will deviate from the tex live current. Best not drop files from the beta into the upcoming tex live but use a separate tree. The next current will be around the context meeting when we also plan to have luatex 0.70+. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Re: [NTG-context] Keeping margin note on the same line
by Vyatcheslav Yatskovsky 05 Jun '10

05 Jun '10

No, no, your idea is exactly what I missed! :) Thanks! > I somehow feel that this is not what you want: > > \def\chorus#1{\startnarrower{\itx CHORUS}\doiftext{#1}{\inmargin{#1}}\stopnarrower} > \starttext > \chorus{} > > \chorus{B} > \stoptext > -- Best Regards, Vyatcheslav Yatskovsky

1 0