Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Thu, 28 Sep 2000 21:44:48 +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 VAA12294 for ; Thu, 28 Sep 2000 21:44:48 +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.11.0/8.10.2) with ESMTP id e8SJimG26027 for ; Thu, 28 Sep 2000 21:44:48 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C02984.8F1F7800" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <11.C38D22DE@mail.listserv.gmd.de>; Thu, 28 Sep 2000 21:44:38 +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 471950 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 28 Sep 2000 21:44:33 +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 VAA01072 for ; Thu, 28 Sep 2000 21:44:05 +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 VAA31762 for ; Thu, 28 Sep 2000 21:44:06 +0200 Received: from knatte.tninet.se (knatte.tninet.se [195.100.94.10]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with SMTP id VAA25884 for ; Thu, 28 Sep 2000 21:44:06 +0200 (MET DST) Received: (qmail 9796 invoked from network); 28 Sep 2000 21:44:01 +0200 Received: from garibaldi.tninet.se (HELO algonet.se) (195.100.94.103) by knatte.tninet.se with SMTP; 28 Sep 2000 21:44:01 +0200 Received: from [195.100.226.171] (du171-226.ppp.su-anst.tninet.se [195.100.226.171]) by garibaldi.tninet.se (BLUETAIL Mail Robustifier 2.2.1) with ESMTP id 910332.170237.970garibaldi-s2 for ; Thu, 28 Sep 2000 21:43:57 +0200 In-Reply-To: References: Your message of "Thu, 28 Sep 2000 10:51:48 +0200." <200009280851.KAA23024@mozart.ujf-grenoble.fr> Return-Path: X-Sender: haberg@pop.matematik.su.se (Unverified) Content-class: urn:content-classes:message Subject: Re: Diacritical marks in Zapf Chancery Date: Thu, 28 Sep 2000 20:42:33 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" 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: 3619 This is a multi-part message in MIME format. ------_=_NextPart_001_01C02984.8F1F7800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 10.02 +0100 0-09-28, Robin Fairbairns wrote: >> (Are all these things really sound on this list?) > >of course they're not; they have absolutely nothing to do with the >development of latex, and would be better dealt with on comp.text.tex ... >we (the latex team) are unlikely to schedule work on bugs that aren't >in our database. people with bugs (rather than infelicities such as >the present problem) should use ... \def\them{LaTeX development team} It is of course up to \them to define the rules of this list as they = please. But generally, the question which standard headers one should have and = what ought to be in them use to be discussed in the Usenet news comp std = groups for say the C/C++ languages. So if similar principles apply to LaTeX, = the prospects of a 8renc.sty file in say the LaTeX base distribution appears = to belong here. (But discussions on how to get around the absence of such a file practically belong somewhere else. :-) ) Another question, which I did not explictly mention but hinted at, ought = to belong to this list, namely what principles to use in error reporting: I think that the normal way for LaTeX to react would be that if there is a likely makeshift substitute, LaTeX might try that, but if the attempts = are more off than that, LaTeX should report an error and stop. I admit, it isn't easy to program LaTeX that way given the shortcomings of TeX, but = now you have a case that departs from that principle. Hans Aberg ------_=_NextPart_001_01C02984.8F1F7800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Diacritical marks in Zapf Chancery

At 10.02 +0100 0-09-28, Robin Fairbairns wrote:
>> (Are all these things really sound on this = list?)
>
>of course they're not; they have absolutely = nothing to do with the
>development of latex, and would be better dealt = with on comp.text.tex
...
>we (the latex team) are unlikely to schedule work = on bugs that aren't
>in our database.  people with bugs (rather = than infelicities such as
>the present problem) should use ...

\def\them{LaTeX development team}

It is of course up to \them to define the rules of = this list as they please.

But generally, the question which standard headers one = should have and what
ought to be in them use to be discussed in the Usenet = news comp std groups
for say the C/C++ languages. So if similar principles = apply to LaTeX, the
prospects of a 8renc.sty file in say the LaTeX base = distribution appears to
belong here. (But discussions on how to get around = the absence of such a
file practically belong somewhere else. :-) )

Another question, which I did not explictly mention = but hinted at, ought to
belong to this list, namely what principles to use in = error reporting: I
think that the normal way for LaTeX to react would be = that if there is a
likely makeshift substitute, LaTeX might try that, = but if the attempts are
more off than that, LaTeX should report an error and = stop. I admit, it
isn't easy to program LaTeX that way given the = shortcomings of TeX, but now
you have a case that departs from that = principle.

  Hans Aberg

------_=_NextPart_001_01C02984.8F1F7800--