Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Mon, 21 Aug 2000 00:06:58 +0200 (MEST) 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 AAA14943 for ; Mon, 21 Aug 2000 00:06:58 +0200 (MEST) MIME-Version: 1.0 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.10.1/8.10.1) with ESMTP id e7KM6ve28834 for ; Mon, 21 Aug 2000 00:06:57 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C00AF2.F549ED00" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <2.2F22145B@mail.listserv.gmd.de>; Mon, 21 Aug 2000 0:06:57 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 468106 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 21 Aug 2000 00:00:25 +0200 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 AAA19416 for ; Mon, 21 Aug 2000 00:00:24 +0200 (MET DST) 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 AAA16530 for ; Mon, 21 Aug 2000 00:00:24 +0200 Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id AAA13239 for ; Mon, 21 Aug 2000 00:00:24 +0200 (MET DST) Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE via smtp-local with ESMTP; Mon, 21 Aug 2000 00:00:19 +0200 Received: from rigel.univie.ac.at (dial-143130.HRZ.Uni-Dortmund.DE [129.217.143.130]) by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id AAA16117; Mon, 21 Aug 2000 00:00:17 +0200 (MET DST) Received: from localhost (sx0005@localhost [127.0.0.1]) by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id TAA27101; Sun, 20 Aug 2000 19:36:47 +0200 In-Reply-To: References: <200008201111.NAA1528264@sg10.chem.tue.nl> Return-Path: X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN) Content-class: urn:content-classes:message Subject: Re: new command Date: Sun, 20 Aug 2000 18:36:43 +0100 Message-ID: <20000820.193643.88488986.sx0005@sx2.hrz.uni-dortmund.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Werner LEMBERG" 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: 3592 This is a multi-part message in MIME format. ------_=_NextPart_001_01C00AF2.F549ED00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > > I am just wandering if in the next version of latex a new command > > (something in the stille of \c or \k) will be created to support the > > Romanian letters S and also T with a comma bellow. Those letters > > are not supported at this moment but they are in the proposal of > > iso-8859-16 (iso-8859-2 provide ones with a cedilla instead). > > if it really _is_ a comma, it's easy to hack up a command using > existing glyphs. It is a comma. OpenType fonts like pala.ttf provide a Romanian locale which will replace the cedilla with a comma. Werner ------_=_NextPart_001_01C00AF2.F549ED00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: new command

> > I am just wandering if in the next version = of latex a new command
> > (something in the stille of \c or \k) will = be created to support the
> > Romanian letters S and also T with a comma = bellow. Those letters
> > are not supported at this moment but they = are in the proposal of
> > iso-8859-16 (iso-8859-2 provide ones with a = cedilla instead).
>
> if it really _is_ a comma, it's easy to hack up = a command using
> existing glyphs.

It is a comma.  OpenType fonts like pala.ttf = provide a Romanian
locale which will replace the cedilla with a = comma.


    Werner

------_=_NextPart_001_01C00AF2.F549ED00--