Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 6 Jan 2003 13:16:16 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h06CGE6C012411 for ; Mon, 6 Jan 2003 13:16:14 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h06C67wO023854; Mon, 6 Jan 2003 13:06:07 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2B57D.692EA800" 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 h064ACYo008642; Mon, 6 Jan 2003 12:59:32 +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 5216 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 6 Jan 2003 12:59:32 +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 h06BxWTk010734 for ; Mon, 6 Jan 2003 12:59:32 +0100 Received: from smtp.wanadoo.es (smtp3.wanadoo.es [62.37.236.137] (may be forged)) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h06C5wEV001653 for ; Mon, 6 Jan 2003 13:05:59 +0100 (MET) Received: from Ordenador-de-Javier-Bezos.local. (62-36-68-83.dialup.uni2.es [62.36.68.83]) by smtp.wanadoo.es (8.11.3/8.11.3) with SMTP id h06BDSk06022 for ; Mon, 6 Jan 2003 12:13:29 +0100 (MET) In-Reply-To: References: <15897.10031.19948.331055@cs.anu.edu.au> Return-Path: X-Mailer: GyazMail version 0.9.3 X-OriginalArrivalTime: 06 Jan 2003 12:16:16.0619 (UTC) FILETIME=[698D1BB0:01C2B57D] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -0.1 () IN_REP_TO,MAY_BE_FORGED,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,WEIRD_PORT Content-class: urn:content-classes:message Subject: Re: Proposed change of policy Date: Mon, 6 Jan 2003 13:06:56 +0100 Message-ID: A<20030106130656259998.GyazMail.jbezos@wanadoo.es> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Proposed change of policy Thread-Index: AcK1fWml2Nl6dA6lT5Ktaa2pbpDOFQ== From: "Javier Bezos" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4396 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2B57D.692EA800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable David: >> But the question then arises: why e-TeX? Why not Omega, an >> e-TeX/Omega hybrid, . . . ? > > Because functionality present in e-TeX is desperately needed for > implementing more versatile output routines than the present, was > explicitly requested by LaTeX project team members and implemented > for their sake. The functionality present in Omega is needed for some critical tasks (at least, I need them more desperately than those in e-TeX). > In contrast, Omega is a moving target and widely undocumented. The > features specific to Omega are rather orthogonal to most of the > problems the LaTeX3 project is tackling. I cannot speak for the LaTeX3 team, but I don's think so. Integrating LaTeX with Unicode, XML, SVG and multilingual environments should be one of the current goals of LaTeX. While it's true Omega is undocumented and its developement somewhat "arcane", I don't see another possibility. Anyway, see the following: =3D=3D=3D=3D=3D=3D=3D Developing and releasing the Omega system: A white paper 16 November 2002, John Plaice and Yannis Haralambous. http://omega.cse.unsw.edu.au:8080/roadmap/white-0.3.pdf An extensible approach to high-quality multilingual typesetting Submitted for publication, October 2002 John Plaice, Yannis Haralambous, and Chris Rowley. http://omega.cse.unsw.edu.au:8080/roadmap/mlim-submission.pdf Programming extensions needed in Omega 21 May 2001, Frank Mittelbach and Chris Rowley. http://omega.cse.unsw.edu.au:8080/roadmap/ex-omega.pdf =3D=3D=3D=3D=3D=3D=3D Javier ------_=_NextPart_001_01C2B57D.692EA800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Proposed change of policy

David:

>> But the question then arises:  why = e-TeX?  Why not Omega, an
>> e-TeX/Omega hybrid, . . . ?
>
> Because functionality present in e-TeX is = desperately needed for
> implementing more versatile output routines than = the present, was
> explicitly requested by LaTeX project team = members and implemented
> for their sake.

The functionality present in Omega is needed for = some
critical tasks (at least, I need them more = desperately than
those in e-TeX).

> In contrast, Omega is a moving target and widely = undocumented.  The
> features specific to Omega are rather orthogonal = to most of the
> problems the LaTeX3 project is tackling.

I cannot speak for the LaTeX3 team, but I don's = think
so. Integrating LaTeX with Unicode, XML, SVG and = multilingual
environments should be one of the current goals of = LaTeX.
While it's true Omega is undocumented and its = developement
somewhat "arcane", I don't see another = possibility.

Anyway, see the following:

=3D=3D=3D=3D=3D=3D=3D
Developing and releasing the Omega system: A white = paper
16 November 2002, John Plaice and Yannis = Haralambous.
    http://o= mega.cse.unsw.edu.au:8080/roadmap/white-0.3.pdf

An extensible approach to high-quality multilingual = typesetting
Submitted for publication, October 2002
John Plaice, Yannis Haralambous, and Chris = Rowley.
    ht= tp://omega.cse.unsw.edu.au:8080/roadmap/mlim-submission.pdf

Programming extensions needed in Omega
21 May 2001, Frank Mittelbach and Chris = Rowley.
    http://om= ega.cse.unsw.edu.au:8080/roadmap/ex-omega.pdf
=3D=3D=3D=3D=3D=3D=3D

Javier

------_=_NextPart_001_01C2B57D.692EA800--