Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 28 Apr 2003 18:00:28 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h3SG0PPQ002767 for ; Mon, 28 Apr 2003 18:00:26 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C30D9F.4976F600" 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 h3SFqva4001113 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Apr 2003 17:52: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 h3SFqee1028704; Mon, 28 Apr 2003 17:52:40 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from abel.math.umu.se (abel.math.umu.se [130.239.20.139]) by rzdspc1.informatik.uni-hamburg.de (8.12.9/8.12.9) with ESMTP id h3SFqXa4001071 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Apr 2003 17:52:34 +0200 (CEST) Received: from [130.239.20.144] (mac144.math.umu.se [130.239.20.144]) by abel.math.umu.se (8.12.3/8.12.3/Debian-6.3) with ESMTP id h3SFqWxj027926; Mon, 28 Apr 2003 17:52:32 +0200 In-Reply-To: <20030428150354.9F3753C6B7@mx01.nexgo.de> References: Return-Path: X-OriginalArrivalTime: 28 Apr 2003 16:00:28.0975 (UTC) FILETIME=[4A0BBBF0:01C30D9F] X-Sender: lars@abel.math.umu.se X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -22.6 () EMAIL_ATTRIBUTION,IN_REP_TO,MIME_LONG_LINE_QP,REFERENCES,REPLY_WITH_QUOTES Content-class: urn:content-classes:message Subject: Re: textcomp once more Date: Mon, 28 Apr 2003 16:51:14 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: textcomp once more Thread-Index: AcMNn0ouwFxPb68HQSC1iLaBHGITHw== From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= To: "Walter Schmidt" Cc: , "Frank Mittelbach" , Status: R X-Status: X-Keywords: X-UID: 4604 This is a multi-part message in MIME format. ------_=_NextPart_001_01C30D9F.4976F600 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 17.03 +0200 2003-04-28, Walter Schmidt wrote: >On Mon, 28 Apr 2003 15:12:34 +0200, Lars Hellstr=F6m wrote: > >>>Indeed, the need for yet another configuration file >>>(textcomp.cfg) does not make me happy.[...] >> >>One could probably have some of these declarations in textcomp.sty = (e.g. >>those for CM families), use the "full TS1" as default, and suggest = that >>font-loading packages contain explicit declarations when they don't = provide >>this default. > >This is not a general solution: You can use a font family >without a package file, only by loading of the .fd file. Note that the code in textcomp.sty only affects the commands when they = are used via encoding defaults. E.g. \UseTextSymbol{TS1}{\textmarried} would also work around the current subset declaration mechanism. It's = not an absolute stopper, but more a way of turning common black blobs into error messages. >Or can we put the character set declaration into the .fd files? That would be nice, but problably no, since the declaration command = isn't in the LaTeX kernel. (FDs cannot load packages.) >>Also, with respect to Euro, it might be possible to fake this (in >>textcomp.mtx) from `C' and `equals'. >>[...] > >This is an option, provided that we find an .mtx algorithm >that works for arbitrary font families. I think even "works reasonably well" would suffice. > >>[...] >>>#4 =3D #5 + "Euro" >>>Most newer fonts provide this. >> >>If Euro can be faked, then there would not be any need for this = distinction. > >Yet I suggest that we keep a subset "without Euro", for the >time being: Even if the idea of faking the Euro turns out >to be feasible, I wont' be able to write the mtx code and >re-make lots of VFs until June. I think I can write the MTX code. >>[...] >>Trivia of the day: The German pronounciation of "Euro" (which I find >>preferable to the English) sounds a lot like the Swedish "Ojr=E5" = (Ojr\aa), >>which is kind of slang, but would translate to English as "Oops!". > >:-)) What is the Swedish pronounciation of Euro? Evro (with swedish pronounciation of `v', so a German would probably = think of it rather as "Ewro"), although there are those who believe all = foreign words should be pronouced as if they were English and hence rather pronounce it as "Jor=E5". Lars ------_=_NextPart_001_01C30D9F.4976F600 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: textcomp once more

At 17.03 +0200 2003-04-28, Walter Schmidt = wrote:
>On Mon, 28 Apr 2003 15:12:34 +0200, Lars = Hellstr=F6m wrote:
>
>>>Indeed, the need for yet another = configuration file
>>>(textcomp.cfg) does not make me = happy.[...]
>>
>>One could probably have some of these = declarations in textcomp.sty (e.g.
>>those for CM families), use the "full = TS1" as default, and suggest that
>>font-loading packages contain explicit = declarations when they don't provide
>>this default.
>
>This is not a general solution:  You can use = a font family
>without a package file, only by loading of the = .fd file.

Note that the code in textcomp.sty only affects the = commands when they are
used via encoding defaults. E.g.

   \UseTextSymbol{TS1}{\textmarried}

would also work around the current subset declaration = mechanism. It's not
an absolute stopper, but more a way of turning common = black blobs into
error messages.

>Or can we put the character set declaration into = the .fd files?

That would be nice, but problably no, since the = declaration command isn't
in the LaTeX kernel. (FDs cannot load = packages.)

>>Also, with respect to Euro, it might be = possible to fake this (in
>>textcomp.mtx) from `C' and `equals'.
>>[...]
>
>This is an option, provided that we find an .mtx = algorithm
>that works for arbitrary font families.

I think even "works reasonably well" would = suffice.

>
>>[...]
>>>#4 =3D #5 + "Euro"
>>>Most newer fonts provide this.
>>
>>If Euro can be faked, then there would not be = any need for this distinction.
>
>Yet I suggest that we keep a subset "without = Euro", for the
>time being:  Even if the idea of faking the = Euro turns out
>to be feasible, I wont' be able to write the mtx = code and
>re-make lots of VFs until June.

I think I can write the MTX code.

>>[...]
>>Trivia of the day: The German pronounciation = of "Euro" (which I find
>>preferable to the English) sounds a lot like = the Swedish "Ojr=E5" (Ojr\aa),
>>which is kind of slang, but would translate = to English as "Oops!".
>
>:-))  What is the Swedish pronounciation of = Euro?

Evro (with swedish pronounciation of `v', so a German = would probably think
of it rather as "Ewro"), although there are = those who believe all foreign
words should be pronouced as if they were English and = hence rather
pronounce it as "Jor=E5".

Lars


------_=_NextPart_001_01C30D9F.4976F600--