- dev-context - NTG Mailing Lists

[contexttest-Bugs][66] problem with \starttablehead
by contexttest-bugs＠foundry.supelec.fr 15 Jan '07

15 Jan '07

Bugs item #66, was opened at 2007-01-15 10:15 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=66&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: problem with \starttablehead Resolution: None Version: None Category: macros Initial Comment: Hello, shouldn't there be a line on the top of each page? \starttext \starttablehead \HL \stoptablehead \starttables[|l|] \NC test \NC\FR \dorecurse{100}{\NC test \NC\MR} \NC test \NC\LR \stoptables \stoptext Peter ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=66&group_id=21

1 0

[contexttest-Bugs][65] \starttables and \AR
by contexttest-bugs＠foundry.supelec.fr 15 Jan '07

15 Jan '07

Bugs item #65, was opened at 2007-01-15 09:59 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=65&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: \starttables and \AR Resolution: None Version: None Category: macros Initial Comment: Hello, with this test file: \starttext \starttables[|l|] \NC bla \NC\AR \stoptables \stoptext I get an error: ERROR: Misplaced \noalign. Peter ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=65&group_id=21

1 0

Re: [dev-context] [NTG-context] ConTeXt 2007.01.12 problem
by Taco Hoekwater 13 Jan '07

13 Jan '07

Sanjoy Mahajan wrote: >>that test should go into the test repos > > > I've committed it to the contexttest repo as > tex/context/base/supp-mis.tex/test-001.tex > > By the way, in dvi mode the file fails unless "mpprocset:=0;" is put in the > \startMPpositiongraphic. Here's the error msg: > > $ texexec --dvi --nonstopmode tex/context/base/supp-mis.tex/test-001.tex > // on "TeX run 2" > ... > [MP as EPS ./to-dvi-mpgraph.4000] [MP color conversion ./to-dvi-mpgraph.4000 > ! Argument of \dodohandleMPcolor has an extra }. > <inserted text> > \par > <to be read again> > } > \includeMPasEPS ...\the \!!heightb }\doinsertfile > }\wd \scratchbox \!!widt.. > > Taco had diagnosed this as due to ConTeXt not handling the new mpost > procsets (hence the mpprocset := 0;). Not sure why that lack doesn't > hurt the run in pdf mode, but perhaps Taco or Hans understand the > reson. The test file that I committed does not have the mpprocset:=0, > so it can be used to test for mpprocset handling in dvi mode. It is a different set of macros. The macros that are used in dvi mode do not convert to pdf, but only convert colorspaces to other colorspaces. I know what is causing it, just not how to fix. Best, Taco

1 0

Re: [dev-context] [NTG-context] ConTeXt 2007.01.12 problem
by Taco Hoekwater 13 Jan '07

13 Jan '07

Norbert Preining wrote: > > Guys, if you manage to get a fixed upstream by tomorrow 7:20am I can do > an upload ...., otherwise you have to wait till monday morning, because > I am leaving for ice climbing. Yes, I just saw that extra line in spec-mis.tex. Updated TL, but only the files in tex/context/base and tex/context/interface. I also saw a small change in tex.rb, but I do not know it if it is important. Hans? Taco

1 0

New Debian packages
by Norbert Preining 12 Jan '07

12 Jan '07

Hi all! I have uploaded new Debian packages for context/context-nonfree to tug.org and Debian. These packages provide a workaround for using new context with texlive in Debian, ie pdftex < 1.40 by creating a symlink /var/lib/texmf/web2c/pdftex -> /var/lib/texmf/web2c/pdfetex If - you already had such a symlink - or you had a directory (but not a link) then upgrade will be smooth and you will not see anything, the directory or symlink will be removed and a link created to pdfetex. But if you have a symlink to some other place than pdfetex then upgrade will break, please remove it first! As soon as texlive 2006/7 with pdftex 1.40 enters Debian we can get rid of this hack. Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining <preining(a)logic.at> Università di Siena Debian Developer <preining(a)debian.org> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- HARBLEDOWN (vb.) To manoeuvre a double mattress down a winding staircase. --- Douglas Adams, The Meaning of Liff

3 4

[contexttest-Feature Requests][63] Allow attribution immediately following quotation blocks
by contexttest-featurerequests＠foundry.supelec.fr 12 Jan '07

12 Jan '07

Feature Requests item #63, was opened at 2007-01-10 04:05 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=63&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: Taco Hoekwater (taco) Assigned to: Nobody (None) Summary: Allow attribution immediately following quotation blocks Version: None Category: Typesetting Initial Comment: See the excerpt from a discussion with Oliver Buerschaper, below. That one uses a \cite command, but it could also be a footnote, or an Author's name or a wikipedia entry. \setupquotation[right={''\footnote{First}}] is not usable because it gets fed into \symbol[] and many things do not work well in that case (the \footnote, for example, disappears). Taco Oliver wrote: >The disappearing footnote may be unfixable within \startquotation. It >> would be easier to define your own start-stop pair for this, because >> \startquotation ... \stopquotation doesn't actually support tacking on >> stuff at the end. Try this instead: >> >> \long\def\startcitedquotation[#1]#2\stopcitedquotation >> {\bgroup \par >> \startnarrower >> \symbol[leftquotation]% >> #2\removeunwantedspaces >> \symbol[rightquotation]% >> \cite[#1] >> \stopnarrower >> \par \egroup} Works like a charm! Thanks very much for the workaround ... I've adapted it slightly so that the optional argument is treated as generic text ... in order to use \cite[], \footnote{\cite[]} or whatever else I need. Could this optional argument perhaps be integrated directly in the usual \startquotation command some day? I guess a lot of people will need this ... every quotation calls for a proper reference ;-) Cheers, Oliver ---------------------------------------------------------------------- >Comment By: Aditya Mahajan (adityam) Date: 2007-01-11 20:55 Message: I think that the reason for \cite and \footnote not working is this because the parameter right is typeset inside a \hsmash. For example see the output of \hsmash{Footnote lost\footnote{test}} I do not know why this is happening, but perhaps the following may help a guru \setbox0=\hbox{This is a test\footnote{Box Zero}} \setbox1=\hbox{This is a test\footnote{Box One}} \box0 %Only footnote mark is present \unhbox1 %Both footnote mark and the footnote is present One way to fix this is to redefine \rightdelimitedmark not to use a \hsmash \def\rightdelimitedtextmark {\delimitedtextparameter\c!right} % was {\hsmash{\delimitedtextparameter\c!right}} I do not know why the \hsmash is there so this may break something. ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=63&group_id=21

1 0

engine setting in context/texexec
by Norbert Preining 11 Jan '07

11 Jan '07

Hi Hans and Taco! I found something interesting, but I couldn't test properly till now: pdftex 1.40.1 sets engine=pdftex (not pdfetex), but texexec puts created formats into web2c/pdfetex, so they won't be found as soon as we have pdftex >= 1.40 around. Is there a way in texexec to adjust this? Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining <preining(a)logic.at> Università di Siena Debian Developer <preining(a)debian.org> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- YEPPOON (n.) One of the hat-hanging corks which Australians wear for making Qantas commercials. --- Douglas Adams, The Meaning of Liff

4 15

Re: [dev-context] Cron <context@server> /var/www/aanhet.net/context/bin/cron/context-mirror
by Taco Hoekwater 10 Jan '07

10 Jan '07

Hi, Hans made a new release yesterday evening. I do not know what is in it (yet), but consider yourself warned :-) Taco Cron Daemon wrote: > receiving file list ... done > ./ > context/beta/ > context/current/ > context/current/cont-exa.zip > context/current/cont-ext.zip > context/current/cont-fnt.zip > context/latest/ > context/current/cont-img.zip > context/current/cont-mpd.zip > context/current/cont-ppc.zip > context/current/cont-tmf.zip > context/current/cont-win.zip

4 9

[contexttest-Bugs][64] texexec --module does not honor --result
by contexttest-bugs＠foundry.supelec.fr 10 Jan '07

10 Jan '07

Bugs item #64, was opened at 2007-01-10 09:57 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=64&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: Aditya Mahajan (adityam) Assigned to: Nobody (None) Summary: texexec --module does not honor --result Resolution: None Version: None Category: scripts Initial Comment: texexec --module --mode=color --color tex/context/third/t-vim.pdf --result=doc/context/third/vim/vim-doc.pdf puts the result in the current directory rather than honoring the --result= directive Aditya ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=64&group_id=21

1 0

texexec and return codes ... bad
by Norbert Preining 10 Jan '07

10 Jan '07

Hi all! (Gerben, you are on the To since you were interested in the ctxfmtutil, but it is bugged ..., see below) texexec does not return a useful return code: # texexec --nonstopmode --fast --make --aleph cont-en ... loading : Context Font Macros / UNICODE Support ! Aleph capacity exceeded, sorry [number of strings=33165]. \setvalue ...xpandafter \def \csname #1\endcsname l.275 \defineucharmapping{\s!default} #1#2% No pages of output. Transcript written on cont-en.log. TeXExec | TeXExec | tex engine path: /etc/texmf/web2c/aleph TeXExec | TeXExec | TeXExec | runtime: 3.104333 # echo $? 0 # This is bad, very bad.... something we can do about it? And, since I am at it: It does not honor the --nonstopmode: # texexec --nonstopmode --fast --make --xetex cont-en ... loading : Context Encoding Macros (pdf) ! Undefined control sequence. l.63 \ifcase\pdfgentounicode \else \expandafter \endinput \fi ? and waiting there. Is there a way to fix these two problems, please??? For Gerben: ctxfmtutil has two problems: - it does not detect if a build was broken due to the first bug - it hangs sometimes due to the second bug Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining <preining(a)logic.at> Università di Siena Debian Developer <preining(a)debian.org> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- FRANT (n.) Measure. The legal minimum distance between two trains on the District and Circle line of the London Underground. A frant, which must be not less than 122 chains (or 8 leagues) long, is not connected in any way with the adjective 'frantic' which comes to us by a completely different route (as indeed do the trains). --- Douglas Adams, The Meaning of Liff

3 8