Mike Bird wrote:

On Friday 12 January 2007 06:43, Alan Bowen wrote:

...

Processing a file that used to typeset successfully now gets the error message:

! Undefined control sequence. \initializenextposition ...dosetpositionpapersize {\printpaperwidth } {\print...

\setposition ...ing \else \initializenextposition \def

Hi Norbert,

context_2007.01.12-1 has this problem. You might want to pull it until a new package is available as this problem is a bit of a showstopper.

Is this a side-effect of context 2007.01.12 demanding pdftex 1.40? Taco

On Fre, 12 Jan 2007, Mike Bird wrote:

...

...

context_2007.01.12-1 has this problem. You might want to pull it until a new package is available as this problem is a bit of a showstopper.

Is this a side-effect of context 2007.01.12 demanding pdftex 1.40?

It's the problem Hans diagnosed as material missing from the end of spec-mis.tex . He said he would upload a new zip but I don't know if that has happened yet.

Damned, this is seriously hosed ... one time I couldn't test all the test cases I have on my laptop before uploading the upstream stuff is hosed, that is a pity. 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. In the meantime please install http://www.tug.org/texlive/Debian/context/context_2007.01.02-2_all.deb to get a working context ... Sorry ... Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining Università di Siena Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- GLENTIES (pl.n.) Series of small steps by which someone who has made a serious tactical error in a conversion or argument moves from complete disagreement to wholehearted agreement. --- Douglas Adams, The Meaning of Liff

Several>> ! Undefined control sequence. Several>> \initializenextposition ...dosetpositionpapersize Taco> There was a new upload at 6pm, but I have not yet tested if that fixes Taco> it. When I upgraded to 2007.01.12 01:02 via the Debian package, I got the same error that others have reported. I just tested 2007.01.12 15:56 and the problem is fixed, so thanks for the quick work. Here is the test file (same as I've been using for dvipos), and it showed the problem in dvi and pdf modes. I'm using pdftex 1.40.0 (with Taco's patch for the off-by-one-error) in /usr/local/bin. ============================================================ \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 ============================================================ -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien)

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. The test skeleton script (./tex/context/base/enco-pfr.tex/Makefile, which by the way I should move to a more general location) uses only pdf mode. I'll move it to a new home and modify it to test dvi mode as well.

(which btw we should get running now that it gets filled up); i have to look into that asap

The ./tex/context/base/enco-pfr.tex/Makefile is a start. But see a previous email included below. I still don't see where to get the known-good comparison PDF (or ps). -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) Date: Fri, 06 Oct 2006 13:16:20 BST From: Sanjoy Mahajan To: contexttest-commits@foundry.supelec.fr Reply-to: contexttest-commits@foundry.supelec.fr Subject: [contexttest] automatic testing [I added an actual subject line and started this msg as a new thread -- sorry for breaking the threading and, in the first instance, for lazily replying to the Cron msg rather than starting a new thread.] Hans Hagen wrote: Sanjoy Mahajan wrote:

Just added a file to test \showframe (broken in the last few beta releases).

Which reminds me that I'm hoping someday to set up automatic testing of new releases. The main item in order to do that: 'known good' outputs for the automatic comparison Makefile to use. Is generating each PDF with the latest non-beta release a good way? It's probably easier than looking at each one by hand, though not as reliable.

we can think of several tests : (1) do they pass (2) does the file has the same number of pages (3) does a bitmap of the page roughly looks the same 1/2 would already be great I have 3 [bitmap checking] pretty much working (see the Makefile in the repository). It was a quick hack so is a bit rigid: It tells you how different the old and new bitmaps are, but a shift of one pixel is interpreted as "very different" (it doesn't do any dynamic programming to do the match, just a simple overlay). For 1 [do they pass], do you mean whether the texexec completes? That should be easy as well. #2 [number of pages] should also be easy, and can be added to #3 pretty easily. But I still want to know "same number of pages as which release?" Because all one has in the repository is .tex source files, but not known correct PDF or log output from a correct run to compare against. Another question is what to do about settings like \runMPgraphics or \runMPTEXgraphics (and write18). For example, static MP figures break (I'm pretty sure) if write18 is on but those other two are off. Should the test files themselves turn on those variables if they are needed (i.e. make any changes relative to the default cont-sys.rme)? [I'll soon visit relatives for the upcoming U.S. long weekend so might not reply for a few days, depends on how lazy I feel about email.] -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1. _______________________________________________ Contexttest-commits mailing list Contexttest-commits@foundry.supelec.fr https://foundry.supelec.fr/mailman/listinfo/contexttest-commits

Taco Hoekwater wrote:.

Is this a side-effect of context 2007.01.12 demanding pdftex 1.40?

this pos stuff is a bit tricky to support in compatible ways because in a sense it's a backend issue as well as multipass. pdftex and now xetex provide it internally since they kind of are the backends too, which in turn makes it a bit messy to fit into the context special feature driver files, etc etc. We still need the dvipos fallback for aleph. 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 -----------------------------------------------------------------