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 f7UNU0932677 for ; Fri, 31 Aug 2001 01:30:00 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f7UNTxT17791 . for ; Fri, 31 Aug 2001 01:30:00 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C131AB.AFB30C00" 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 f7UNTxJ13668 for ; Fri, 31 Aug 2001 01:29:59 +0200 (MET DST) 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 BAA21728 for ; Fri, 31 Aug 2001 01:29:59 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 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 f7UNTwJ13664 for ; Fri, 31 Aug 2001 01:29:58 +0200 (MET DST) 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 f7UNT4b06805; Fri, 31 Aug 2001 01:29:04 +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 f7UNSHo04514; Fri, 31 Aug 2001 01:28:17 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0058 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 31 Aug 2001 01:28:13 +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 f7UNSDo04508 for ; Fri, 31 Aug 2001 01:28:13 +0200 Received: from wisbech.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.15]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f7UNSwb06791 for ; Fri, 31 Aug 2001 01:28:58 +0200 (MET DST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=rf) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 15cbF4-0004jU-00 for LATEX-L@listserv.uni-heidelberg.de; Fri, 31 Aug 2001 00:28:58 +0100 In-Reply-To: Your message of "Fri, 31 Aug 2001 00:29:08 +0300." Return-Path: Content-class: urn:content-classes:message Subject: Re: LaTeX3 and Omega Date: Fri, 31 Aug 2001 00:28:58 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robin Fairbairns" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4147 This is a multi-part message in MIME format. ------_=_NextPart_001_01C131AB.AFB30C00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > One of the goals of the LaTeX3 project is to > > "...provide access to arbitrary fonts from any family (such as the > POSTSCRIPT and TrueType fonts) including a wide range of fonts for > multi-lingual documents and the specialist glyphs required by > documents in various technical and academic areas." > > Currently the only typesetting engine capable to provide these > facilities is Omega. actually, within an appropriate universe of discourse, one can claim that tex itself does just the same. what omega adds in this area is ease of dealing with fonts appropriate to exotic languages (for some definition of "exotic"). > So, is it reasonable to assume that the LaTeX3 > will be actually an Omega format? since work is already under way to consider the issues involved in mounting existing latex on omega, i would expect latex3 will also run over omega. i do not expect latex3 to be an omega-exclusive format: indeed, i would imagine that any such restriction would constitute a kiss of death to latex3 ... and it's going to have a hard enough time of it in any case ;-) > Moreover, since Omega provides a number > of commands that can be used to specify the writting direction, isn't > reasonable to expect formatting commands to have an optional > writting direction specifier, e.g., > > \begin{center}[LRL] > arabic or hebrew text > \end{center} > > or even better > > \begin{center}[Arabic] > arabic or hebrew text > \end{center} i'm not expert on current multi-lingual-latex thinking, but i don't expect that sort of construct to be present as a "primitive". (of course, such contructs could not be added to latex2e, since they would invalidate current documents.) robin ------_=_NextPart_001_01C131AB.AFB30C00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX3 and Omega

>     One of the goals of the = LaTeX3 project is to
>
>   "...provide access to arbitrary = fonts from any family (such as the
>    POSTSCRIPT and TrueType fonts) = including a wide range of fonts for
>    multi-lingual documents and = the specialist glyphs required by
>    documents in various technical = and academic areas."
>
>    Currently the only typesetting = engine capable to provide these
> facilities is Omega.

actually, within an appropriate universe of discourse, = one can claim
that tex itself does just the same.  what omega = adds in this area is
ease of dealing with fonts appropriate to exotic = languages (for some
definition of "exotic").

> So, is it reasonable to assume that the = LaTeX3
> will be actually an Omega format?

since work is already under way to consider the issues = involved in
mounting existing latex on omega, i would expect = latex3 will also run
over omega.  i do not expect latex3 to be an = omega-exclusive format:
indeed, i would imagine that any such restriction = would constitute a
kiss of death to latex3 ... and it's going to have a = hard enough time
of it in any case ;-)

> Moreover, since Omega provides a number
> of commands that can be used to specify the = writting direction, isn't
> reasonable to expect formatting commands to have = an optional
> writting direction specifier, e.g.,
>
> \begin{center}[LRL]
>    arabic or hebrew text
> \end{center}
>
> or even better
>
> \begin{center}[Arabic]
>    arabic or hebrew text
> \end{center}

i'm not expert on current multi-lingual-latex = thinking, but i don't
expect that sort of construct to be present as a = "primitive".  (of
course, such contructs could not be added to latex2e, = since they would
invalidate current documents.)

robin

------_=_NextPart_001_01C131AB.AFB30C00--