- ntg-context - Mailing Lists

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

macro beginner question
by Bernhard Rosensteiner 05 Jun '10

05 Jun '10

Hello all, in the process of learning macro programming in context i encountered the following problem (minimal example is attached): When i have \setuphead[section][color={red}] the color key influences in a strange way my „novice macro“ (see the text which should be black but is red). Further more the \ruledhbox in my macro stops at some point the red color (with a normal \hbox all the text in the section is red). what i´m doing wrong here? I don’t expect such a behaviour best regards Bernhard

2 4

Keeping margin note on the same line
by Vyatcheslav Yatskovsky 05 Jun '10

05 Jun '10

Hello, Please, advise me. Is there a way to keep margin text and body text on the same line in the following situation? \define[0]\chorus{\startnarrower{\itx CHORUS}\stopnarrower} \starttext \chorus \chorus \inmargin{B}\chorus \stoptext Now "B" is above "CHORUS", I want it to be exactly on the same line. Regards, Vyatcheslav

2 1

macro beginner question...
by Bernhard Rosensteiner 05 Jun '10

05 Jun '10

Hello all, in the process of learning macro programming in context i encountered the following problem (minimal example is attached): when i have \setuphead[section][color={red}] the color key influences in a strange way my „novice macro“ (see the text which should be black but is red). Further more the \ruledhbox in my macro stops at some point the red color (with a normal \hbox all the text in the section is red). what i´m doing wrong here? best regards Bernhard

1 0

3. Re: \MPpos, pxy, initialize_box(), oh my! (Hongwen Qiu)
by Adam Fuller 05 Jun '10

05 Jun '10

On 5/06/2010 6:31 a.m., ntg-context-request(a)ntg.nl wrote: > 3. Re: \MPpos, pxy, initialize_box(), oh my! (Hongwen Qiu) hi hongwen, thanks for taking an interest. my initial post had a mistake: i meant to refer to the /Metafun/ manual, not the Metapost manual. that probably didn't help. 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. 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

2 1

\section{\inmargin{}} doesn't work in MkIV
by Rogutės Sparnuotos 04 Jun '10

04 Jun '10

I've quickly run a (MkII) document under MkIV after updating to 2010.05.27, but it didn't compile (perhaps this is related to the other interaction bugs in MkIV): \setupinteraction[state=start] \starttext \section{\inmargin{}} \stoptext -- -- Rogutės Sparnuotos

2 2

floatcombinations, localfloats [mkiv]
by Thomas Floeren 04 Jun '10

04 Jun '10

Hello, I can't get floatcombinations to work in mkiv: \starttext \placefigure [none]{} {\startfloatcombination [2*1] \placefigure {.}% {\externalfigure [.]} \placefigure {.}% {\externalfigure [.]} \stopfloatcombination} \stoptext (some definitions are missing: forcelocalfloats, resetlocalfloats, noflocalfloats) Best wishes Thomas This is LuaTeX, Version beta-0.60.1-2010052906 (Web2C 2010/pretest) (rev 3685) ConTeXt ver: 2010.06.01 00:18 MKIV fmt: 2010.6.1 int: english/english

5 6

Wrong spacing before and after commas in math(?)
by "Stefan Müller" 04 Jun '10

04 Jun '10

Hi, if I'm typesetting for example $(a,x,\dots,b)$ I see that the space before the x is too small. It should be bigger than the space after the x. I could work around it by typing $a,\,x,\dots,\,b$ but this is somewhat inconvenient and even a bit too much spacing... On the other hand, the spacing before \dots is just right, but the spacing after \dots is too small: the spaces between commas and periods ",...," should all be the same. Is this a bug? Can this be changed by a global option or something? Thanks for any help in advance. Best regards, Stefan -- _______ ey, leute, ich hab so lange gebraucht um mir plan a auszudenken, fragt jetzt doch nicht auch noch nach plan b! GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

4 3