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 f1BKpWH12146 for ; Sun, 11 Feb 2001 21:51:32 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1BKpVd26293 . for ; Sun, 11 Feb 2001 21:51:31 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0946C.69DF6200" 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 f1BKpVM14732 for ; Sun, 11 Feb 2001 21:51:31 +0100 (MET) 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 VAA25379 for ; Sun, 11 Feb 2001 21:51:30 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 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 f1BKpUM14728 for ; Sun, 11 Feb 2001 21:51:30 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <0.3D5A656D@mail.listserv.gmd.de>; Sun, 11 Feb 2001 21:51:23 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487795 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 11 Feb 2001 21:51:27 +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 VAA26805 for ; Sun, 11 Feb 2001 21:51:25 +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 VAA33434 for ; Sun, 11 Feb 2001 21:51:26 +0100 Received: from Sina.sharif.ac.ir (sina.Sharif.AC.IR [194.225.40.9]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1BKo6u22039 for ; Sun, 11 Feb 2001 21:50:30 +0100 (MET) Received: from localhost (roozbeh@localhost) by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id AAA18971 for ; Mon, 12 Feb 2001 00:19:22 +0330 In-Reply-To: <14982.49654.241503.82704@istrati.zdv.uni-mainz.de> Return-Path: X-Sender: roozbeh@Sina.sharif.ac.ir Content-class: urn:content-classes:message Subject: Re: hyphenation morass Date: Sun, 11 Feb 2001 21:49:22 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Roozbeh Pournader" 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: 3819 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0946C.69DF6200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sun, 11 Feb 2001, Frank Mittelbach wrote: > a) UTF8 isn't seasier to parse for LaTeX than LICR if the LICR is not = UTF8 > that is :-) since LaTeX has the parser for LICR built in and for UTF8 = you have > to add it 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. > 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. --roozbeh ------_=_NextPart_001_01C0946C.69DF6200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: hyphenation morass

On Sun, 11 Feb 2001, Frank Mittelbach wrote:

> a) UTF8 isn't seasier to parse for LaTeX than = LICR if the LICR is not UTF8
> that is :-) since LaTeX has the parser for LICR = built in and for UTF8 you have
> to add it

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.

> 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.

--roozbeh

------_=_NextPart_001_01C0946C.69DF6200--