Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 6 Jun 2003 00:11:21 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h55MBIPQ020661 for ; Fri, 6 Jun 2003 00:11:19 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C32BAF.64FBCA80" Received: from sun.dante.de (root@sun.dante.de [134.100.9.52]) by rzdspc1.informatik.uni-hamburg.de (8.12.9/8.12.9) with ESMTP id h55MB2ch015480 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Jun 2003 00:11:03 +0200 (CEST) Received: from rzdspc1.informatik.uni-hamburg.de (rzdspc1.informatik.uni-hamburg.de [134.100.9.61]) by sun.dante.de (8.12.9/8.12.9) with ESMTP id h55MARHS024121 for ; Fri, 6 Jun 2003 00:10:27 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from wisbech.cl.cam.ac.uk (IDENT:3S3Zf2suXJ9Li+0wcLaF/HuPWm3+N+8q@mta1.cl.cam.ac.uk [128.232.0.15]) by rzdspc1.informatik.uni-hamburg.de (8.12.9/8.12.9) with ESMTP id h55MAOcg015439 for ; Fri, 6 Jun 2003 00:10:25 +0200 (CEST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=[WJKAiJB0FuqDnnNBQt6o+qhZwNNT3upt]) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 19O2wA-00019V-00; Thu, 05 Jun 2003 23:10:22 +0100 In-Reply-To: Your message of Thu, 05 Jun 2003 21:30:52 +0300. Return-Path: X-OriginalArrivalTime: 05 Jun 2003 22:11:21.0742 (UTC) FILETIME=[656D02E0:01C32BAF] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -7.2 () IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1 Content-class: urn:content-classes:message Subject: Re: announce: inputenc support for utf8 Date: Thu, 5 Jun 2003 23:10:21 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: announce: inputenc support for utf8 Thread-Index: AcMrr2ea8ZacZgFQRRCFqaifhnRiJw== From: "Robin Fairbairns" To: "Apostolos Syropoulos" Cc: Status: R X-Status: X-Keywords: X-UID: 4626 This is a multi-part message in MIME format. ------_=_NextPart_001_01C32BAF.64FBCA80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > > see what happened to cyrillic: there is T2(A-C) which are official > > LaTeX encodings as well as X2 which is an extended encoding where > > you are on your own. If there will be a greek encoding (or more) > > that fit those restrictions needed for multi-lingual processing > > then adding utf8 support will be possible without much fuss. >=20 > Okay, but we need a new name for the Greek encoding: LGR is not a = proper > name. Currently there are two basic Greek encodings ISO-8859-7 and > Windows-1253 (their only difference is the slot reserved for Capital > Alpha with tonos) and so I believe one file can be used for both > encodings. So who will ``allocate'' the new encoding name? it looks to me as if iso 8859-7 isn't appropriate as an output encoding for a tex-based engine, because of problems with uc/lc tables. (of course, this need not be a problem with omega, but that's not today's problem.) specifically, code points C0 and E0 should be an uc/lc pair, but are in fact iota-dieresis-tonos and upsilon-dieresis-tonos. contrariwise, Alpha-tonos is B6, whereas alpha-tonos is DC, Epsilon-tonos is B8, epsilon-tonos is DD. similar problems with [Ii]ota-tonos, [Oo]micron-tonos, [Uu]psilon-tonos and [Oo]mega-tonos. also terminal sigma is in a letter slot with nothing 32 characters down. i think there's some rather serious thinking to be done before specifying an output font for greek in latex. :-( (i really ought to have worked on it before, but what with one thing and another...) i'm afraid i'm not going to eurotex, so can't take part in any discussions about the matter. (i have to spend some time in cambridge this summer, what with visiting greece for another greek language course last week.) sigh: a priori it seemed a good idea. robin ------_=_NextPart_001_01C32BAF.64FBCA80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: announce: inputenc support for utf8

> > see what happened to cyrillic: there is = T2(A-C) which are official
> > LaTeX encodings as well as X2 which is an = extended encoding where
> > you are on your own. If there will be a = greek encoding (or more)
> > that fit those restrictions needed for = multi-lingual processing
> > then adding utf8 support will be possible = without much fuss.
>
> Okay, but we need a new name for the Greek = encoding: LGR is not a proper
> name. Currently there are two basic Greek = encodings ISO-8859-7 and
> Windows-1253 (their only difference is the slot = reserved for Capital
> Alpha with tonos) and so I believe one file can = be used for both
> encodings. So who will ``allocate'' the new = encoding name?

it looks to me as if iso 8859-7 isn't appropriate as = an output
encoding for a tex-based engine, because of problems = with uc/lc
tables.  (of course, this need not be a problem = with omega, but that's
not today's problem.)

specifically, code points C0 and E0 should be an uc/lc = pair, but are
in fact iota-dieresis-tonos and = upsilon-dieresis-tonos.

contrariwise, Alpha-tonos is B6, whereas alpha-tonos = is DC,
Epsilon-tonos is B8, epsilon-tonos is DD.  = similar problems with
[Ii]ota-tonos, [Oo]micron-tonos, [Uu]psilon-tonos and = [Oo]mega-tonos.

also terminal sigma is in a letter slot with nothing = 32 characters
down.

i think there's some rather serious thinking to be = done before
specifying an output font for greek in latex.  = :-(  (i really ought to
have worked on it before, but what with one thing and = another...)

i'm afraid i'm not going to eurotex, so can't take = part in any
discussions about the matter.  (i have to spend = some time in cambridge
this summer, what with visiting greece for another = greek language
course last week.)

sigh: a priori it seemed a good idea.

robin

------_=_NextPart_001_01C32BAF.64FBCA80--