Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sun, 4 May 2003 17:07:15 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h44F7BPQ024035 for ; Sun, 4 May 2003 17:07:13 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3124E.D8C45380" 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 h44F6vlq007535 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 4 May 2003 17:06:58 +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 h44F6Se1013341; Sun, 4 May 2003 17:06:28 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from postman.arcor.de (postman1.arcor-online.net [151.189.0.187]) by rzdspc1.informatik.uni-hamburg.de (8.12.9/8.12.9) with ESMTP id h44F6Nlq007501 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 4 May 2003 17:06:23 +0200 (CEST) Received: from localhost (dialin-145-254-228-140.arcor-ip.net [145.254.228.140]) (authenticated bits=0) by postman.arcor.de (8.12.9/8.12.9) with SMTP id h44F6J73012236; Sun, 4 May 2003 17:06:21 +0200 (MEST) In-Reply-To: <16051.47545.433641.880408@istrati.mittelbach-online.de> Return-Path: X-Mailer: PMMail 2.20.2380 for OS/2 Warp 4.0 X-OriginalArrivalTime: 04 May 2003 15:07:15.0869 (UTC) FILETIME=[D948ECD0:01C3124E] 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 15:18:46 +0100 Message-ID: <200305041506.h44F6J73012236@postman.arcor.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: textcomp once more Thread-Index: AcMSTtltV6TO5hwgSImW0ka1s2bD8g== From: "Walter Schmidt" To: "Frank Mittelbach" Cc: , =?iso-8859-1?Q?Lars_Hellstr=F7m?= , Reply-To: "Walter Schmidt" Status: R X-Status: X-Keywords: X-UID: 4609 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3124E.D8C45380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sat, 3 May 2003 14:44:41 +0200, Frank Mittelbach wrote: >with proper documentation=20 Are you really going to add a chapter about textcomp.sty to the usrguide? I can hardly believe it ;-) >the default should be 5 so that using textcomp is safe by default.=20 In this case, lots of existing documents which are loading textcomp.sty without an option and generate _correct_ output nowadays, will generate errors or even wrong symbols (i.e. faked symbols, or symbols from the wrong typeface, depending on the implementation). This anything else than "safe", and it clashes with ther current policy of strict compatibility. I know that I'm repeating myself. We discussed this already more than once, but I'm still not going to say "yes" to your suggestion. =20 >if that produces an error then the user has two >options: > > - add the font to the cfg Ha, ha, ha! Do you seriously expect the average LaTeX user to understand 1) what this means and 2) how this is done? > - do \usepackage[almostfull]{textcomp} % thereby modifying the default Why not the other way round? The "proper" documentation should say clearly: "If you want to be warned about missing symbols, load textcomp.sty with the option [iso-adobe]. However, be aware that certain symbols which are actually available in a font, may become unusable then". After all, this is the truth, isn't it?=20 --=20 Walter ------_=_NextPart_001_01C3124E.D8C45380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: textcomp once more

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 = ;-)

>the default should be 5 so that using textcomp is = safe by default.

In this case, lots of existing documents which are = loading
textcomp.sty without an option and generate _correct_ = output
nowadays, will generate errors or even wrong symbols = (i.e.
faked symbols, or symbols from the wrong typeface, = depending
on the implementation).  This anything else than = "safe", and
it clashes with ther current policy of strict = compatibility.

I know that I'm repeating myself.  We discussed = this already
more than once, but I'm still not going to say = "yes" to your
suggestion. 

>if that produces an error then the user has = two
>options:
>
> - add the font to the cfg

Ha, ha, ha!  Do you seriously expect the average = LaTeX user
to understand 1) what this means and 2) how this is = done?

> - do \usepackage[almostfull]{textcomp} % thereby = modifying the default

Why not the other way round?  The = "proper" documentation
should say clearly:  "If you want to be = warned about missing
symbols, load textcomp.sty with the option = [iso-adobe].
However, be aware that certain symbols which are = actually
available in a font, may become unusable = then".  After all,
this is the truth, isn't it?

--
Walter




------_=_NextPart_001_01C3124E.D8C45380--