January 2007 - dev-context - NTG Mailing Lists

Update type-gyr.tex
by Aditya Mahajan 07 Jan '07

07 Jan '07

Hi Hans, Attached the an updated type-gyr.tex file with support for schola. This is my first attempt to modify a typescript file, so be careful. Aditya

1 0

two dvipos fixes so that it works with ConTeXt
by Sanjoy Mahajan 06 Jan '07

06 Jan '07

[Karl and Norbert CC'ed in case dvipos is going into their trees] The dvipos I have (cvs'ed from cvs.ktug.or.kr:/home/cvsroot) needs two fixes for it to work with the 2007.01.02 context (and maybe with earlier versions too). This is on Ubuntu i386, texlive 2005. Try this file with 'texexec --dvi --nobackend' to see the problems -- or if there are none, let me know why it works for you! =================== begin: to-dvi.tex ================== \defineoverlay [foregraphics] [\positionoverlay{foregraphics}] \setupbackgrounds [page] [background={foreground,foregraphics}] \starttext \hpos{r23}{7} \quad \hpos{r24}{8} \startMPpositiongraphic{mypos:line} mpprocset := 0; % context doesn't yet handle the new mpprocsets path pa, pb, pab ; numeric na, nb ; initialize_box(\MPpos{\MPvar{from}}) ; na := nxy ; pa := llxy..lrxy..urxy..ulxy..cycle ; initialize_box(\MPpos{\MPvar{to}}) ; nb := nxy ; pb := llxy..lrxy..urxy..ulxy..cycle ; if na=nb : pab := center pa -- center pb ; pab := pab cutbefore (pab intersectionpoint pa) ; pab := pab cutafter (pab intersectionpoint pb) ; pickup pencircle; draw pab; anchor_box(\MPanchor{\MPvar{from}}) ; fi ; \stopMPpositiongraphic \startpositionoverlay{foregraphics} \setMPpositiongraphic{r23}{mypos:line}{to=r24} \stoppositionoverlay The pattern. \stoptext =================== end: to-dvi.tex ================== Problems: 1. The dvipos output is in sp (but without labelling that), which confuses the next run of ConTeXt. So the first patch makes dvipos append 'sp' to the coordinates it outputs. That change was easier than hacking the tex macros that parses the output. 2. After that is fixed, the coordinates are wrong, so running the above file again crashes because the boxes are in the wrong place and the paths no longer intersect. The second patch corrects this problem, which is caused by dvipos parsing the dvi file incorrectly. Maybe ConTeXt used to output the dimens in the pos: \special in sp? Anyway, the special now looks like (see to-dvi.dvi): pos:pxywhd "text:1" 426.78743pt 597.51323pt 0.0pt which was being parsed by dvipos as 426 etc. and assumed to be sp, so it was writing junk to to-dvi.tuo file, and the next run was failing becaues the boxes were in the wrong location. So I made dvipos read in floats with 'pt' appended, then convert them to sp. By the way, what is the 'list' that dvipos is looking for after the three dimens above? If anything needs a \pospxyplus, it'll be in trouble since I think 'list' scanf target is not being parsed, so the var remains uninitialized. -Sanjoy `A nation of slaves is always prepared to applaud the clemency of their master who, in the abuse of absolute power, does not proceed to the last extremes of injustice and oppression.' (Gibbon) # HG changeset patch # User Sanjoy Mahajan <sanjoy(a)mrao.cam.ac.uk> # Date 1168136989 18000 # Node ID 13a3c8c608ddcfbb569f1925fc0a64fcd25f7344 # Parent c184bfb52c9425d7e7a87105e9f17ac874be657e Append sp (scaled point) unit to un-dimensioned coordinates diff -r c184bfb52c94 -r 13a3c8c608dd dvicore.c --- a/dvicore.c Sat Jan 06 21:28:59 2007 -0500 +++ b/dvicore.c Sat Jan 06 21:29:49 2007 -0500 @@ -924,11 +924,11 @@ static void do_pos_special (unsigned cha y = max_v - dvi_state.v; if (strcmp(cmd, "pos:pxy") == 0) - fprintf(outfp, "\\pospxy{%s}{%d}{%ld}{%ld}\n", tag, current_page, x, y); + fprintf(outfp, "\\pospxy{%s}{%d}{%ldsp}{%ldsp}\n", tag, current_page, x, y); else if (strcmp(cmd, "pos:pxywhd") == 0) - fprintf(outfp, "\\pospxywhd{%s}{%d}{%ld}{%ld}{%ld}{%ld}{%ld}\n", tag, current_page, x, y, w, h, d); + fprintf(outfp, "\\pospxywhd{%s}{%d}{%ldsp}{%ldsp}{%ldsp}{%ldsp}{%ldsp}\n", tag, current_page, x, y, w, h, d); else if (strcmp(cmd, "pos:pxyplus") == 0) - fprintf(outfp, "\\pospxyplus{%s}{%d}{%ld}{%ld}{%ld}{%ld}{%ld}{%ld}\n", tag, current_page, x, y, w, h, d, list); + fprintf(outfp, "\\pospxyplus{%s}{%d}{%ldsp}{%ldsp}{%ldsp}{%ldsp}{%ldsp}{%ld}\n", tag, current_page, x, y, w, h, d, list); else if (strcmp(cmd, "pos:begbox") == 0) new_bbox(tag, BOX_TYPE); else if (strcmp(cmd, "pos:endbox") == 0) # HG changeset patch # User Sanjoy Mahajan <sanjoy(a)mrao.cam.ac.uk> # Date 1168137910 18000 # Node ID f30b6ea9f33e3b3825c4e2b923fd73d88869ae1e # Parent 13a3c8c608ddcfbb569f1925fc0a64fcd25f7344 Read w,h,d in pt (not sp) from dvi file Maybe ConTeXt used to give the dimens in the \specials in sp? Anyway, the special now looks like: pos:pxywhd "text:1" 426.78743pt 597.51323pt 0.0pt which was being parsed before as 426 etc. and assumed to be sp. diff -r 13a3c8c608dd -r f30b6ea9f33e dvicore.c --- a/dvicore.c Sat Jan 06 21:29:49 2007 -0500 +++ b/dvicore.c Sat Jan 06 21:45:10 2007 -0500 @@ -918,7 +918,15 @@ static void do_pos_special (unsigned cha for (p++; p - buffer < buffer_len && isspace(*p); p++) ; /* skip white chars */ if (p - buffer < buffer_len) - sscanf(p, "%ld %ld %ld %ld", &w, &h, &d, &list); + { + float w_f, h_f, d_f; /* in pt */ + /* what the hell is list? */ + sscanf(p, "%fpt %fpt %fpt %ld", &w_f, &h_f, &d_f, &list); + /* convert to sp. Forget about rounding (add 0.5 if you want it). */ + w = w_f * 65536; + h = h_f * 65536; + d = d_f * 65536; + } x = dvi_state.h + denominator / 100; y = max_v - dvi_state.v;

1 0

[contexttest-Feature Requests][59] interaction and hyphenation
by contexttest-featurerequests＠foundry.supelec.fr 05 Jan '07

05 Jan '07

Feature Requests item #59, was opened at 2007-01-04 13:20 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=59&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: interaction and hyphenation Version: None Category: None Initial Comment: It would be nice, to be able to hyphenate interaction texts. Example with overfull \hbox: \setupinteraction[state=start] \definereferenceformat[inFig][text=Abbildung] \starttext \placefigure[][fig1]{bla}{bla} \dorecurse{58}x, siehe \inFig[fig1]. \stoptext Peter ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2007-01-05 18:07 Message: This is not so much a bug as a feature request. Hans says: Can perhaps be implemented later when there is better low-level support for text attributes in TeX (luatex) ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=59&group_id=21

1 0

[contexttest-Bugs][52] original-adobe-euro.map for dvips
by contexttest-bugs＠foundry.supelec.fr 05 Jan '07

05 Jan '07

Bugs item #52, was opened at 2007-01-04 12:07 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=52&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: original-adobe-euro.map for dvips Resolution: None Version: None Category: None Initial Comment: When creating dvi and ps output with following input: \usesymbols[eur] \starttext \texteuro \stoptext no euro-symbol shows up. dvips does not understand the map file. Peter ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2007-01-05 17:36 Message: The output from the texexec --dvi case looks good at first glance. I do not have the font installed myself, but you could try adding the PostScript font names in that map file (this will not harm pdftex): euromo EuroMono-Regular <euromo.pfb euromob EuroMono-Bold <euromob.pfb euromoi EuroMono-Italic <euromoi.pfb euromobi EuroMono-BoldItalic <euromobi.pfb eurosa EuroSans-Regular <eurosa.pfb eurosab EuroSans-Bold <eurosab.pfb eurosai EuroSans-Italic <eurosai.pfb eurosabi EuroSans-BoldItalic <eurosebi.pfb eurose EuroSerif-Regular <eurose.pfb euroseb EuroSerif-Bold <euroseb.pfb eurosei EuroSerif-Italic <eurosei.pfb eurosebi EuroSerif-BoldItalic <eurosebi.pfb ---------------------------------------------------------------------- Comment By: Peter Münster (peter) Date: 2007-01-05 17:26 Message: When using texexec --dvi, the file in pdftex is read and dvips outputs this: This is dvips(k) 5.96 Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2007.01.05:1712' -> test.ps <tex.pro><lm-ec.enc><texps.pro>. <eurose.pfb><lmr12.pfb>[1]

1 0

[contexttest-Bugs][52] original-adobe-euro.map for dvips
by contexttest-bugs＠foundry.supelec.fr 05 Jan '07

05 Jan '07

Bugs item #52, was opened at 2007-01-04 12:07 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=52&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: original-adobe-euro.map for dvips Resolution: None Version: None Category: None Initial Comment: When creating dvi and ps output with following input: \usesymbols[eur] \starttext \texteuro \stoptext no euro-symbol shows up. dvips does not understand the map file. Peter ---------------------------------------------------------------------- Comment By: Peter Münster (peter) Date: 2007-01-05 17:26 Message: When using texexec --dvi, the file in pdftex is read and dvips outputs this: This is dvips(k) 5.96 Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2007.01.05:1712' -> test.ps <tex.pro><lm-ec.enc><texps.pro>. <eurose.pfb><lmr12.pfb>[1]

1 0

[contexttest-Bugs][61] clipping in dvi-mode
by contexttest-bugs＠foundry.supelec.fr 05 Jan '07

05 Jan '07

Bugs item #61, was opened at 2007-01-05 16:49 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=61&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: clipping in dvi-mode Resolution: None Version: None Category: macros Initial Comment: \clip does not work in dvi-mode: \starttext \startuseMPgraphic{test} mpprocset:=0; draw fullcircle scaled 4cm withpen pencircle scaled 1cm ; setbounds currentpicture to boundingbox fullcircle scaled 4cm ; \stopuseMPgraphic \ruledhbox{\useMPgraphic{test}} \vskip3cm \doifmode{*dvi}{Nothing to see here, only an empty box:} \ruledhbox{\clip{\useMPgraphic{test}}} \stoptext Peter Münster ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=61&group_id=21

1 0

[contexttest-Bugs][49] \startmathalign gives an extra formula number
by contexttest-bugs＠foundry.supelec.fr 05 Jan '07

05 Jan '07

Bugs item #49, was opened at 2007-01-04 01:27 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=49&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ >Status: Closed Priority: 3 Submitted By: Aditya Mahajan (adityam) Assigned to: Nobody (None) Summary: \startmathalign gives an extra formula number Resolution: None Version: None Category: macros Initial Comment: The following code gives an exra line with formla number \placeformula \startformula \startalign \NC a \EQ b \NR[+] \NC c \EQ d \NR[+] \stopalign \stopformula ---------------------------------------------------------------------- >Comment By: Aditya Mahajan (adityam) Date: 2007-01-05 03:38 Message: This is corrected in the latest beta. Problem in a nutshell: (by Taco) Correct old: math-pln.tex:\def\displ@y{.....} core-mat.tex:\let\normaldispl@y\displ@y core- mat.tex:\def\displ@y{\resetdisplaymatheq\normaldispl@y} Broken old: core-mat.tex:\let\normaldispl@y\displ@y core- mat.tex:\def\displ@y{\resetdisplaymatheq\normaldispl@y} math-pln.tex:\def\displ@y{.....} New: core-mat.tex:\def\displ@y{.....} core-mat.tex:\let\normaldispl@y\displ@y core- mat.tex:\def\displ@y{\resetdisplaymatheq\normaldispl@y} ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=49&group_id=21

1 0

Re: [dev-context] [NTG-context] Problems with "mathalign"
by Aditya Mahajan 05 Jan '07

05 Jan '07

(changed lists) On Wed, 3 Jan 2007, Taco Hoekwater wrote: > Aditya Mahajan wrote: > > > > > > I can confirm that there is an extra number. I do not know what is > > causing this. I am not aware of anything in core-mat has changed. > > There is that extra stuff in \everymathematics. Could that be it? The file runs fine with ConTeXt 2006-11-24 19:15 so it is something in the last month. (This version is available as the windows stand alone distribution from pragma's website.) Changes in the last 5 weeks to math related files are changes in math-pln.tex. I do not know who these could have caused trouble. The \let\next$ change in core-mat. I reverted back to \def\next{$} inside a test file, and this does not seem to trouble. The colon definitions inside math-tex.tex, they should not cause any problem, unless I redefined a core command. (I do not think so). Some slight changes in math-ext.tex, but that was a wrong definition of harpoons. So, it is either the \everymathematics change, or a change in some macro that is called by \placeformula. Aditya

3 5

Script files for third party modules.
by Aditya Mahajan 04 Jan '07

04 Jan '07

Hi Hans, Mojca and I are writing a module that uses a vim script to highlight source code. What is the best way to "package" this module. That is, where should the script file go? The ideal location will be scripts/context/vim/macros/ Are third party modules allowed to "pollute" the scripts/ directory? We have another concern while calling the script. We need to call vim using vim [options] -c "source path-to-script/2context.vim" filename This command is called using \externalprogram. We do not want to hard code the location of path to the scirpt. Does it make sense to add VIMINPUTS environment variable to texmfstart, to reduce the search time? Is there a way to locate the file in the texmf-tree and pass the arguments to another program? I copied 2context.vim to texmf-tree and texmfstart --locate 2context.vim gives its location. However texmfstart bin:vim kpse:2context.vim does not load the file. I get texmfstart version 2.0.2 kpse : direct (forced) locating '2context.vim' in program space 'context' locating '2context.vim' in program space 'context' using format 'other text files' 2context.vim is not resolved using 'system' call: vim 2context.vim What is the correct way of finding something in the texmf-tree but outside program space 'context'? Aditya

3 21

[contexttest-Bugs][60] interaction between boldmath and text-mode
by contexttest-bugs＠foundry.supelec.fr 04 Jan '07

04 Jan '07

Bugs item #60, was opened at 2007-01-04 13:21 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=60&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: interaction between boldmath and text-mode Resolution: None Version: None Category: None Initial Comment: Hello, in text-mode, the µ gets slanted, when boldmath is used: %% To get upshaped \textmu: \usetypescript[modern][texnansi] \setupbodyfont[modern] %% Defining boldmath: \definetypeface[boldmath][mm][boldmath][modern] %% To get bold everywhere: \def\myBF{\boldmath\rm\bf} \starttext {\myBF bla $bla$ \textmu} % \textmu is slanted here \stoptext (Workaround: {{\myBF bla $bla$} \bf\textmu}) Peter ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=60&group_id=21

1 0