Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 24 Jan 2003 22:43:42 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0OLhe6C018570 for ; Fri, 24 Jan 2003 22:43:41 +0100 MIME-Version: 1.0 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0OLYUXM018879; Fri, 24 Jan 2003 22:34:30 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C3F1.A99D7B00" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0O3PCTp014696; Fri, 24 Jan 2003 22:26:58 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 9496 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 24 Jan 2003 22:26:58 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0OLQw5f023017 for ; Fri, 24 Jan 2003 22:26:58 +0100 Received: from mailrelay1.lrz-muenchen.de (mailrelay1.lrz-muenchen.de [129.187.254.101]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0OLYCXM018814 for ; Fri, 24 Jan 2003 22:34:13 +0100 (MET) Received: from pc-e21-23.frm2.tu-muenchen.de by mailrelay1.lrz-muenchen.de with ESMTP for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 24 Jan 2003 22:34:07 +0100 Received: from localhost (localhost [127.0.0.1]) by pc-e21-23.frm2.tu-muenchen.de (8.11.6/8.10.1/SuSE Linux 8.9.3-0.1) with ESMTP id h0OLXPx23971 for ; Fri, 24 Jan 2003 22:33:25 +0100 In-Reply-To: <15921.37877.396653.396158@istrati.mittelbach-online.de> Return-Path: X-OriginalArrivalTime: 24 Jan 2003 21:43:45.0020 (UTC) FILETIME=[AB6A4BC0:01C2C3F1] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -2.7 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_03_05,USER_AGENT_PINE Content-class: urn:content-classes:message Subject: Re: [LATEX3] endless loop in xmarks with book class? Date: Fri, 24 Jan 2003 22:33:25 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [LATEX3] endless loop in xmarks with book class? Thread-Index: AcLD8auMdZRhudWrQ6e7xVgbIfzd0A== From: "Bjoern Pedersen" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4496 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C3F1.A99D7B00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Fri, 24 Jan 2003, Frank Mittelbach wrote: > Bjoern Pedersen writes: > > > I am currently doing some testing with the xor-package. > > If I use book.cls, it goes in an inifite loop in the = mark-processing. > > > > If anybody has a fix, I would be interessted. > > \renewcommand\chaptermark[1]{} > > this is not a fix but a workaround. Good, this will help getting me started again. > reason for the problem: xor uses multiple marks ie xmarks.dtx provides = a > different mark structure than std latex has. > > you can get into similar problems if you say in latex something like > \mark{foo}, ie if you do not preserve the fact that current latex = requires a > mark to consist of exactly 2 groups, eg \mark{{foo}{bar}} internally. > > now the mark mechanism for pagelayout hasn't been done so far, thus if = you > combine the new OR with the old \pagestyle interface : "bomb*" So I will try to get something on the way. > we always wondered if it would be too tight for use in a production = system. > > > A minimal test-file will follow during the weekend. > > fast, didn't know we had already weekend :-) > Well, your answer was almost as fast, thanks a lot. Bj=F6rn -- Bjoern Pedersen Lichtenbergstr.1 Technische Universitaet Muenchen D-85747 Garching ZBE Instrumentierung FRM-II Tel. + 49 89 289-14707 Fax -14666 ------_=_NextPart_001_01C2C3F1.A99D7B00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [LATEX3] endless loop in xmarks with book class?

On Fri, 24 Jan 2003, Frank Mittelbach wrote:

> Bjoern Pedersen writes:
>
>  > I am currently doing some testing = with the xor-package.
>  > If I use book.cls,  it goes in = an inifite loop in the mark-processing.
>  >
>  > If anybody has a fix, I would be = interessted.
>
> \renewcommand\chaptermark[1]{}
>
> this is not a fix but a workaround.

Good, this will help getting me started again.

> reason for the problem: xor uses multiple marks = ie xmarks.dtx provides a
> different mark structure than std latex = has.
>
> you can get into similar problems if you say in = latex something like
> \mark{foo}, ie if you do not preserve the fact = that current latex requires a
> mark to consist of exactly 2 groups, eg = \mark{{foo}{bar}} internally.
>
> now the mark mechanism for pagelayout hasn't = been done so far, thus if you
> combine the new OR with the old \pagestyle = interface : "bomb*"

So I will try to get something on the way.

> we always wondered if it would be too tight for = use in a production system.
>
>  > A minimal test-file will follow = during the weekend.
>
> fast, didn't know we had already weekend = :-)
>

Well, your answer was almost as fast, thanks a = lot.

 Bj=F6rn

--
Bjoern = Pedersen           = ;            =   Lichtenbergstr.1
Technische Universitaet = Muenchen        D-85747 = Garching
ZBE Instrumentierung FRM-II
 Tel. + 49 89 289-14707 Fax -14666

------_=_NextPart_001_01C2C3F1.A99D7B00--