From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/32713 Path: news.gmane.org!not-for-mail From: Sanjoy Mahajan Newsgroups: gmane.comp.tex.context,gmane.linux.debian.devel.tetex Subject: Re: ConTeXt 2007.01.12 problem Date: Sat, 13 Jan 2007 14:10:55 +0000 Message-ID: References: <45A89DD8.7040508@wxs.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1168697579 30582 80.91.229.12 (13 Jan 2007 14:12:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 13 Jan 2007 14:12:59 +0000 (UTC) Cc: debian-tex-maint@lists.debian.org Original-X-From: ntg-context-bounces@ntg.nl Sat Jan 13 15:12:56 2007 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by lo.gmane.org with esmtp (Exim 4.50) id 1H5jcp-0004m7-UB for gctc-ntg-context-518@m.gmane.org; Sat, 13 Jan 2007 15:12:51 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 3753120135; Sat, 13 Jan 2007 15:09:00 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12730-01; Sat, 13 Jan 2007 15:08:59 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 48D112012E; Sat, 13 Jan 2007 15:07:12 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 880352012B for ; Sat, 13 Jan 2007 15:07:10 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11975-02-11 for ; Sat, 13 Jan 2007 15:07:05 +0100 (CET) Original-Received: from mraos.ra.phy.cam.ac.uk (mraos.ra.phy.cam.ac.uk [131.111.48.8]) by ronja.ntg.nl (Postfix) with ESMTP id 7498420127 for ; Sat, 13 Jan 2007 15:07:05 +0100 (CET) Original-Received: from skye.ra.phy.cam.ac.uk ([131.111.48.158] ident=mail) by mraos.ra.phy.cam.ac.uk with esmtp (Exim 4.43) id 1H5jax-00020D-UY; Sat, 13 Jan 2007 14:10:55 +0000 Original-Received: from sanjoy by skye.ra.phy.cam.ac.uk with local (Exim 3.36 #1) id 1H5jax-0004dA-00; Sat, 13 Jan 2007 14:10:55 +0000 Original-To: mailing list for ConTeXt users In-Reply-To: Your message of "Sat, 13 Jan 2007 09:52:40 +0100." <45A89DD8.7040508@wxs.nl> X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.7 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:32713 gmane.linux.debian.devel.tetex:20431 Archived-At: > 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 }. \par } \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