Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Thu, 28 Sep 2000 22:26:56 +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 WAA17073 for ; Thu, 28 Sep 2000 22:26:55 +0200 (MEST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0298A.71EDA800" 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 e8SKQtG28664 for ; Thu, 28 Sep 2000 22:26:55 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <14.ABAA3FBC@mail.listserv.gmd.de>; Thu, 28 Sep 2000 22:26:55 +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 471976 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 28 Sep 2000 22:26:04 +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 WAA01655 for ; Thu, 28 Sep 2000 22:26:03 +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 WAA31834 for ; Thu, 28 Sep 2000 22:26:03 +0200 Received: from wisbech.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.15]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id WAA01737 for ; Thu, 28 Sep 2000 22:26:02 +0200 (MET DST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=rf) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 13ekFm-0003jf-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Thu, 28 Sep 2000 21:26:02 +0100 In-Reply-To: Your message of "Thu, 28 Sep 2000 21:42:33 +0200." Return-Path: Content-class: urn:content-classes:message Subject: Re: what is and what isn't meet for this list (was Diacritical marks) Date: Thu, 28 Sep 2000 21:26:02 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robin Fairbairns" 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: 3621 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0298A.71EDA800 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. :-) ) i'm afraid you're wrong. \we (before my time) set up this list as a means to discuss the future of latex in the development of latex 3. some time back, i suspect before you were on the scene, there was another mailing list for discussing the development of latex 2e; that list has now been closed --- the decisions about what's to be in 2e have all been made long since. anything that's definitely missing from the conception of of latex2e may be a candidate for a bug report (category: change request), but creating a random new encoding structure within latex for apparent symmetry's sake doesn't meet my metric of "definitely missing". 8r is an intermediate encoding developed to facilitate mapping between knuth's dotty ot1 encoding and the cork meeting's dotty t1 encoding, and adobe's standard encoding (8a in tex terms). no-one rationally uses it for any other purpose. that there are some latex control files relating to it is probably (walter schmidt may choose to correct me) an accident of the way the psnfss metrics are generated. if you want a more nearly rational encoding, i would strongly recommend investigating ly1, for which a full set of bits and pieces is to be found on the archives, written for and placed in the public arena by[*], y&y. Robin Fairbairns, Cambridge [*] i don't actually recall the licensing conditions, but since the stuff is in tetex it's certainly some sort of free licence. ------_=_NextPart_001_01C0298A.71EDA800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: what is and what isn't meet for this list (was = Diacritical marks)

> 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. :-) = )

i'm afraid you're wrong.  \we (before my time) = set up this list as a
means to discuss the future of latex in the = development of latex 3.
some time back, i suspect before you were on the = scene, there was
another mailing list for discussing the development = of latex 2e; that
list has now been closed --- the decisions about = what's to be in 2e
have all been made long since.  anything that's = definitely missing
from the conception of of latex2e may be a candidate = for a bug report
(category: change request), but creating a random new = encoding
structure within latex for apparent symmetry's sake = doesn't meet my
metric of "definitely missing".

8r is an intermediate encoding developed to facilitate = mapping between
knuth's dotty ot1 encoding and the cork meeting's = dotty t1 encoding,
and adobe's standard encoding (8a in tex = terms).  no-one rationally
uses it for any other purpose.  that there are = some latex control
files relating to it is probably (walter schmidt may = choose to correct
me) an accident of the way the psnfss metrics are = generated.

if you want a more nearly rational encoding, i would = strongly
recommend investigating ly1, for which a full set of = bits and pieces
is to be found on the archives, written for and = placed in the public
arena by[*], y&y.

Robin Fairbairns, Cambridge

[*] i don't actually recall the licensing conditions, = but since the
stuff is in tetex it's certainly some sort of free = licence.

------_=_NextPart_001_01C0298A.71EDA800--