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 f1BLqWH12296 for ; Sun, 11 Feb 2001 22:52:32 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1BLqVd26498 . for ; Sun, 11 Feb 2001 22:52:32 +0100 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 f1BLqUM17369 for ; Sun, 11 Feb 2001 22:52:30 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09474.EF671000" Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA03154 for ; Sun, 11 Feb 2001 22:52:30 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1BLqUM17365 for ; Sun, 11 Feb 2001 22:52:30 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <0.C2727C48@mail.listserv.gmd.de>; Sun, 11 Feb 2001 22:52:22 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487860 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 11 Feb 2001 22:52:25 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id WAA28040 for ; Sun, 11 Feb 2001 22:52:19 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id WAA20582 for ; Sun, 11 Feb 2001 22:52:19 +0100 Received: from moutvdom01.kundenserver.de (moutvdom01.kundenserver.de [195.20.224.200]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1BLqJu03886 for ; Sun, 11 Feb 2001 22:52:19 +0100 (MET) Received: from [195.20.224.209] (helo=mrvdom02.schlund.de) by moutvdom01.kundenserver.de with esmtp (Exim 2.12 #2) id 14S4Pk-0000oz-00 for LATEX-L@urz.uni-heidelberg.de; Sun, 11 Feb 2001 22:52:12 +0100 Received: from manz-3e364896.pool.mediaways.net ([62.54.72.150] helo=istrati.zdv.uni-mainz.de) by mrvdom02.schlund.de with esmtp (Exim 2.12 #2) id 14S4QJ-0001US-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 11 Feb 2001 22:52:47 +0100 Received: (from latex3@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id WAA13281; Sun, 11 Feb 2001 22:35:56 +0100 In-Reply-To: References: <14982.49654.241503.82704@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: VM 6.75 under Emacs 20.4.1 X-Authentication-Warning: istrati.zdv.uni-mainz.de: latex3 set sender to frank@mittelbach-online.de using -f Content-class: urn:content-classes:message Subject: Re: hyphenation morass Date: Sun, 11 Feb 2001 22:35:56 +0100 Message-ID: <14983.1468.365576.638652@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3825 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09474.EF671000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Roozbeh, > I was talking about using other tools. You can have Perl scripts, for > example, that take UTF-8, and generate anything you want to use. You = may > distribute these generated versions before the internal UTF-8 support = in > LaTeX. yeah, but most people wouldn't like that would they, if everything else = did work perfectly without in the past. not sure this would create = acceptance. if you want to do conversion then you could argue that (at least = currently the conversion should be done the other way around, ie have files directly readable by LaTeX, eg in its current LICR, and have the perl convert = those files to utf8 (not problem bidirectional) for, say omega if they would = be useful there. --- by the way, are they useful? (guess i asked that before) > > ps is there anybody at the other end of omega-developers-list being = interested > > on a unified version of LaTeX supporting omega and tex? as you may = have seen > > (since i know you are on it) i've written up a couple of comments = and ideas > > regarding Javiers drafts but was even more stonewalled than it = sometimes > > happens on this list. > > That should be problem of the sourceforge config. Yannis and John are > sometimes very busy, you know. so they are, so am I; but i wasn't complaining and stonewalled was the = wrong word, i meant "met with silence" so basically i was wondering if this = ever reached or not? stuff like Re: Lambda -- draft (components) because if not it should perhaps be resend frank ------_=_NextPart_001_01C09474.EF671000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: hyphenation morass

Roozbeh,

 > I was talking about using other tools. You = can have Perl scripts, for
 > example, that take UTF-8, and generate = anything you want to use. You may
 > distribute these generated versions before = the internal UTF-8 support in
 > LaTeX.

yeah, but most people wouldn't like that would they, = if everything else did
work perfectly without in the past. not sure this = would create acceptance.

if you want to do conversion then you could argue that = (at least currently the
conversion should be done the other way around, ie = have files directly
readable by LaTeX, eg in its current LICR, and have = the perl convert those
files to utf8 (not problem bidirectional) for, say = omega if they would be
useful there.

--- by the way, are they useful? (guess i asked that = before)


 > > ps is there anybody at the other end = of omega-developers-list being interested
 > > on a unified version of LaTeX = supporting omega and tex? as you may have seen
 > > (since i know you are on it) i've = written up a couple of comments and ideas
 > > regarding Javiers drafts but was even = more stonewalled than it sometimes
 > > happens on this list.
 >
 > That should be problem of the sourceforge = config. Yannis and John are
 > sometimes very busy, you know.

so they are, so am I; but i wasn't complaining and = stonewalled was the wrong
word, i meant "met with silence" so = basically i was wondering if this ever
reached = <omega-system-devel@lists.sourceforge.net> or not? stuff = like

  Re: Lambda -- draft  (components)

because if not it should perhaps be resend

frank

------_=_NextPart_001_01C09474.EF671000--