Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f7VJSc906646 for ; Fri, 31 Aug 2001 21:28:38 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f7VJSWT24015 . for ; Fri, 31 Aug 2001 21:28:32 +0200 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f7VJSVJ13682 for ; Fri, 31 Aug 2001 21:28:31 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13253.222AF700" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id VAA22517 for ; Fri, 31 Aug 2001 21:28:30 +0200 (MEST) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f7VJSUJ13677 for ; Fri, 31 Aug 2001 21:28:30 +0200 (MET DST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f7VJQfb25107; Fri, 31 Aug 2001 21:26:41 +0200 (MET DST) Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f7VJPso11602; Fri, 31 Aug 2001 21:25:54 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1230 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 31 Aug 2001 21:25:52 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f7VJPqo11596 for ; Fri, 31 Aug 2001 21:25:52 +0200 Received: from naf1.mathematik.uni-tuebingen.de (naf1.mathematik.uni-tuebingen.de [134.2.161.197]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f7VJQdb25101 for ; Fri, 31 Aug 2001 21:26:39 +0200 (MET DST) Received: from na13.mathematik.uni-tuebingen.de (na13 [134.2.161.180]) by naf1.mathematik.uni-tuebingen.de (8.9.3+Sun/8.9.3) with ESMTP id VAA01132 for ; Fri, 31 Aug 2001 21:26:39 +0200 (MET DST) Received: (from oliver@localhost) by na13.mathematik.uni-tuebingen.de (8.9.3+Sun/8.9.1) id VAA15916; Fri, 31 Aug 2001 21:26:38 +0200 (MET DST) In-Reply-To: <15247.55490.840782.239441@istrati.zdv.uni-mainz.de> References: <15247.27772.447636.809305@istrati.zdv.uni-mainz.de> <15247.55490.840782.239441@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: VM 6.88 under Emacs 20.7.2 X-Authentication-Warning: na13.mathematik.uni-tuebingen.de: oliver set sender to oliver@na.uni-tuebingen.de using -f Content-class: urn:content-classes:message Subject: Re: LaTeX3 and Omega Date: Fri, 31 Aug 2001 20:26:38 +0100 Message-ID: <15247.58606.766844.169216@na.uni-tuebingen.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Marcel Oliver" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4163 This is a multi-part message in MIME format. ------_=_NextPart_001_01C13253.222AF700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach writes: > > Good news, I think. Formerly, in the discussion previous to the > > meeting in Tsukuba, Omega was only *another* possibility, even in = your > > messages. (In other words, I didn't misinterpret the Robin's = opinion > > as the team's opinion, I just included a "deprecated" opinion > > ;-) ) Now Omega is the main candidate (if the suggested = improvements > > are fulfilled in a successor, of course) by far. > > well yes, but what i was indicating in my last message is that i wont = be able > to put as much time into it than i had originally hoped --- so it is = up to you > (plural) to help or even make it happen. > > as i said, we have covered a lot of ground in Metz so there are specs = (though > incomplete) and i wouldn't mind seeing discussions on those on a = broader scale > (either on this list or elsewhere). problem is that i don't know when = i will > find the time to make those specs available (some of them exist only = in John's > scrapbook and as huge jepg's since i photographed the pages :-) > > and i don't know what the state of the whole enterprise is (at the = other side > of the world that is --- John wanted to put some students onto it to = test > certain ideas) that's something that needs finding out. People = seriously > interested in putting more than one or the other email into it should = indicate > that; we might then be able to to get something going after all I'd be willing to put in some effort in documentation, something more concrete than the stuff I wrote up this spring. However, I will be off-line from Sunday until October 12, so this is more medium term. > frank > > > ps on the more easier aspects of a future LaTeX (as it isn't so much = depending > on the underlying formatter): has anybody ever bothered to look at = the new > frontmatter stuff that i presented in Metz and put onto the WWW just = before > the holiday time? if so i would be interested in some comments; = personally i > thought it does its job rather well, but not hearing anything either = way makes > me wonder ... I tried the frontmatter stuff. It so good that it doesn't lend itself to cheap-shot criticism. I think it's really necessary to code up a few real-world journal front matter pages to see if there are real shortcomings. Two things which came up when I was doing front-matter stuff some time back, taking a lot of time to sort out, and do not seem to be covered by the current prototype: - Some specs say "start this element x cm from the top of the page". In other words, can we do absolute rather than relative addressing of layout elements on the page? - Often specs call for letter spacing. This issue is strictly speaking outside your domain of concern, and purists will say "get a letterspaced font". However, such fonts are not easily acquired (in particular if there are other constraints on font selection). In any case, we probably need a well-defined letterspace API. As a first "backend" one could take the Phil Taylor/Donald Arsenau hack, which works very nicely for most practical purposes (but is certainly easy to break). The next best solution could be a clean implementation within a future Omega. Finally, in the case that letterspaced fonts are available, they should certainly be used. Hopefully I'll get to look at the actual code more closely, but not any time soon. Best, Marcel ------_=_NextPart_001_01C13253.222AF700 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX3 and Omega

Frank Mittelbach writes:
 >  > Good news, I think. Formerly, = in the discussion previous to the
 >  > meeting in Tsukuba, Omega was = only *another* possibility, even in your
 >  > messages. (In other words, I = didn't misinterpret the Robin's opinion
 >  > as the team's opinion, I just = included a "deprecated" opinion
 >  > ;-) ) Now Omega is the main = candidate (if the suggested improvements
 >  > are fulfilled in a successor, = of course) by far.
 >
 > well yes, but what i was indicating in my = last message is that i wont be able
 > to put as much time into it than i had = originally hoped --- so it is up to you
 > (plural) to help or even make it = happen.
 >
 > as i said, we have covered a lot of ground = in Metz so there are specs (though
 > incomplete) and i wouldn't mind seeing = discussions on those on a broader scale
 > (either on this list or elsewhere). = problem is that i don't know when i will
 > find the time to make those specs = available (some of them exist only in John's
 > scrapbook and as huge jepg's since i = photographed the pages :-)
 >
 > and i don't know what the state of the = whole enterprise is (at the other side
 > of the world that is --- John wanted to = put some students onto it to test
 > certain ideas) that's something that needs = finding out. People seriously
 > interested in putting more than one or the = other email into it should indicate
 > that; we might then be able to to get = something going after all

I'd be willing to put in some effort in documentation, = something more
concrete than the stuff I wrote up this spring.  = However, I will be
off-line from Sunday until October 12, so this is = more medium term.

 > frank
 >
 >
 > ps on the more easier aspects of a future = LaTeX (as it isn't so much depending
 > on the underlying formatter): has anybody = ever bothered to look at the new
 > frontmatter stuff that i presented in Metz = and put onto the WWW just before
 > the holiday time? if so i would be = interested in some comments; personally i
 > thought it does its job rather well, but = not hearing anything either way makes
 > me wonder ...

I tried the frontmatter stuff.  It so good that = it doesn't lend itself
to cheap-shot criticism.  I think it's really = necessary to code up a
few real-world journal front matter pages to see if = there are real
shortcomings.

Two things which came up when I was doing front-matter = stuff some time
back, taking a lot of time to sort out, and do not = seem to be covered
by the current prototype:

- Some specs say "start this element x cm from = the top of the page".
  In other words, can we do absolute rather than = relative addressing
  of layout elements on the page?

- Often specs call for letter spacing.  This = issue is strictly
  speaking outside your domain of concern, and = purists will say "get a
  letterspaced font".  However, such = fonts are not easily acquired (in
  particular if there are other constraints on = font selection).

  In any case, we probably need a well-defined = letterspace API.

  As a first "backend" one could take = the Phil Taylor/Donald Arsenau
  hack, which works very nicely for most = practical purposes (but is
  certainly easy to break).  The next best = solution could be a clean
  implementation within a future Omega.  = Finally, in the case that
  letterspaced fonts are available, they should = certainly be used.

Hopefully I'll get to look at the actual code more = closely, but not
any time soon.

Best,

Marcel

------_=_NextPart_001_01C13253.222AF700--