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 f7V8Px901449 for ; Fri, 31 Aug 2001 10:25:59 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f7V8PwT20237 . for ; Fri, 31 Aug 2001 10:25:59 +0200 MIME-Version: 1.0 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f7V8PwG00705 for ; Fri, 31 Aug 2001 10:25:58 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C131F6.8FF50580" 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 KAA00267 for ; Fri, 31 Aug 2001 10:25:57 +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 f7V8PrJ17427 for ; Fri, 31 Aug 2001 10:25:57 +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 f7V8MKb08148; Fri, 31 Aug 2001 10:22:20 +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 f7V8LYo06734; Fri, 31 Aug 2001 10:21:34 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0334 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 31 Aug 2001 10:21:31 +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 f7V8LVo06728 for ; Fri, 31 Aug 2001 10:21:31 +0200 Received: from smtp.wanadoo.es ([62.37.236.135]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f7V8MGb08130 for ; Fri, 31 Aug 2001 10:22:16 +0200 (MET DST) Received: from [62.37.82.47] (62-37-82-47.dialup.uni2.es [62.37.82.47]) by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id f7V8LvK16576 for ; Fri, 31 Aug 2001 10:21:58 +0200 (MEST) In-Reply-To: Return-Path: User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 x-mime-autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id f7V8LVo06729 Content-class: urn:content-classes:message Subject: Re: LaTeX3 and Omega Date: Fri, 31 Aug 2001 10:27:15 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Javier Bezos" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4149 This is a multi-part message in MIME format. ------_=_NextPart_001_01C131F6.8FF50580 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"). IMO, adopting Omega for the coming LaTeX3 could provide the quantum leap TeX and LaTeX need. TeX is definitely stalled, despite the many and useful improvements thanks to \special, and Omega allows to automate lots of tasks required by non-"exotic" languages like Spanish (so that I can write ''contrarreloj=B4=B4 instead of ''contra"rreloj=B4=B4=B4), German ("ck) or Portugese. Particularly annoying is Turkish, where you must write ''f{}i=B4=B4 always (or modify several hundreds of metric files...). >> So, is it reasonable to assume that the LaTeX3 >> will be actually an Omega format? I dream about that. Multilingual support for a dual TeX/Omega LaTeX could be a mess to users and developpers. But I'm just dreaming, since the LaTeX team has said in this list that LaTeX3 will be a dual system. > 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 ;-) I think exactly the opposite -- Omega will give live to LaTeX while "old" TeX will be a burden. Javier ------_=_NextPart_001_01C131F6.8FF50580 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").

IMO, adopting Omega for the coming LaTeX3 could = provide the quantum
leap TeX and LaTeX need. TeX is definitely stalled, = despite the
many and useful improvements thanks to \special, and = Omega allows
to automate lots of tasks required by = non-"exotic" languages like
Spanish (so that I can write ''contrarreloj=B4=B4 = instead of
''contra"rreloj=B4=B4=B4), German ("ck) or = Portugese. Particularly
annoying is Turkish, where you must write = ''f{}i=B4=B4 always (or
modify several hundreds of metric files...).

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

I dream about that. Multilingual support for a dual = TeX/Omega
LaTeX could be a mess to users and developpers. But = I'm
just dreaming, since the LaTeX team has said in this = list that
LaTeX3 will be a dual system.

> 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 ;-)

I think exactly the opposite -- Omega will give live = to LaTeX while
"old" TeX will be a burden.

Javier

------_=_NextPart_001_01C131F6.8FF50580--