Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 5 May 2003 00:47:59 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h44MltPQ025032 for ; Mon, 5 May 2003 00:47:57 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3128F.35DFF980" 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 h44Mljlq006425 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 5 May 2003 00:47:45 +0200 (CEST) Received: from rzdspc1.informatik.uni-hamburg.de (root@rzdspc1.informatik.uni-hamburg.de [134.100.9.61]) by sun.dante.de (8.12.9/8.12.9) with ESMTP id h44MlSe1015317; Mon, 5 May 2003 00:47:29 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from wisbech.cl.cam.ac.uk (IDENT:QOCR9jDVBxAce4sIMQw1QyhfXRlU2oai@mta1.cl.cam.ac.uk [128.232.0.15]) by rzdspc1.informatik.uni-hamburg.de (8.12.9/8.12.9) with ESMTP id h44MlOlp006399; Mon, 5 May 2003 00:47:25 +0200 (CEST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=[24WeaxT7lnzTggEeDqPoszvMsMKkFQDB]) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 19CSGS-0005YN-00; Sun, 04 May 2003 23:47:24 +0100 In-Reply-To: Your message of Sun, 04 May 2003 17:56:59 +0200. <16053.14411.19419.666172@istrati.mittelbach-online.de> Return-Path: X-OriginalArrivalTime: 04 May 2003 22:47:59.0157 (UTC) FILETIME=[35F7EE50:01C3128F] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -19.8 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REPLY_WITH_QUOTES Content-class: urn:content-classes:message Subject: Re: textcomp once more Date: Sun, 4 May 2003 23:47:24 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: textcomp once more Thread-Index: AcMSjzYnx9ASML3qR1eIUi6y25B2lg== From: "Robin Fairbairns" To: "Frank Mittelbach" Cc: "Walter Schmidt" , , =?iso-8859-1?Q?Lars_Hellstr=F7m?= , Status: R X-Status: X-Keywords: X-UID: 4613 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3128F.35DFF980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable frank wrote: > Walter Schmidt writes: > > On Sat, 3 May 2003 14:44:41 +0200, Frank Mittelbach wrote: > >=20 > > >with proper documentation=20 > >=20 > > Are you really going to add a chapter about textcomp.sty to > > the usrguide? I can hardly believe it ;-) >=20 > there is an encguide.tex that was never made publically available, = perhaps it > is one day sigh. i dawdled with that for ages, because i was convinced that the model it was describing wasn't complete. i was actually thinking about T1 encoding and fonts with adobe standard glyph complement, but the argument here is exactly the same one. there is almost no font designed by someone other than a texie that covers any one of our font encodings. the problem arises elsewhere. for example, there's a script font somewhere on ctan that covers the upper-case set of T1; and sure enough the author has provided t1*.fd files to go with it. the initial reaction is that this is a _bad_ _thing_, but that is wrong: the benefit of [T1]{fontenc} _should_ be available when using such a font. this argument should clarify the ground on which the document stands, if i ever get it back from whoever-it-was who wanted to work on it for a presentation. robin ------_=_NextPart_001_01C3128F.35DFF980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: textcomp once more

frank wrote:

> Walter Schmidt writes:
>  > On Sat, 3 May 2003 14:44:41 +0200, = Frank Mittelbach wrote:
>  >
>  > >with proper documentation
>  >
>  > Are you really going to add a chapter = about textcomp.sty to
>  > the usrguide?  I can hardly = believe it ;-)
>
> there is an encguide.tex that was never made = publically available, perhaps it
> is one day

sigh.  i dawdled with that for ages, because i = was convinced that the
model it was describing wasn't complete.  i was = actually thinking
about T1 encoding and fonts with adobe standard glyph = complement, but
the argument here is exactly the same one.  = there is almost no font
designed by someone other than a texie that covers = any one of our font
encodings.

the problem arises elsewhere.  for example, = there's a script font
somewhere on ctan that covers the upper-case set of = T1; and sure
enough the author has provided t1*.fd files to go = with it.  the
initial reaction is that this is a _bad_ _thing_, but = that is wrong:
the benefit of [T1]{fontenc} _should_ be available = when using such a
font.

this argument should clarify the ground on which the = document stands,
if i ever get it back from whoever-it-was who wanted = to work on it for
a presentation.

robin

------_=_NextPart_001_01C3128F.35DFF980--