Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 28 Apr 2003 19:38:02 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h3SHbxPQ003025 for ; Mon, 28 Apr 2003 19:38:00 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C30DAC.EAB87900" 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 h3SHbCa4011415 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Apr 2003 19:37:12 +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 h3SHawe1029216; Mon, 28 Apr 2003 19:36:58 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mx12.arcor-online.net (mx12.arcor-online.net [151.189.8.88]) by rzdspc1.informatik.uni-hamburg.de (8.12.9/8.12.9) with ESMTP id h3SHaqa4011388 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 28 Apr 2003 19:36:53 +0200 (CEST) Received: from localhost (dialin-145-254-228-033.arcor-ip.net [145.254.228.33]) by mx12.arcor-online.net (Postfix) with SMTP id E4741133093; Mon, 28 Apr 2003 19:36:50 +0200 (CEST) In-Reply-To: Return-Path: X-Mailer: PMMail 2.20.2380 for OS/2 Warp 4.0 X-OriginalArrivalTime: 28 Apr 2003 17:38:03.0260 (UTC) FILETIME=[EB78BBC0:01C30DAC] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -9.9 () EMAIL_ATTRIBUTION,IN_REP_TO Content-class: urn:content-classes:message Subject: Re: textcomp once more Date: Mon, 28 Apr 2003 18:35:00 +0100 Message-ID: <20030428173650.E4741133093@mx12.arcor-online.net> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: textcomp once more Thread-Index: AcMNrOurbb6PglDHTLus6nXwRv+rOQ== From: "Walter Schmidt" To: =?iso-8859-1?Q?Lars_Hellstr=F6m?= Cc: , "Frank Mittelbach" , Reply-To: "Walter Schmidt" Status: R X-Status: X-Keywords: X-UID: 4605 This is a multi-part message in MIME format. ------_=_NextPart_001_01C30DAC.EAB87900 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C30DAC.EAB87900" ------_=_NextPart_002_01C30DAC.EAB87900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Mon, 28 Apr 2003 17:51:14 +0200, Lars Hellstr=F6m wrote: >>>font-loading packages contain explicit declarations when=20 >>>they don't provide this default. >> >>This is not a general solution: [...] > > \UseTextSymbol{TS1}{\textmarried} > >would also work around the current subset declaration mechanism. It's = not >an absolute stopper, ACK. >>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.) Ok, forget my suggestion. > [re. faking the Euro] >>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. That's what I meant. >[...]=20 >I think I can write the MTX code. TIA! =20 I'll be happy to update the VFs in the PSNFSS collection (and those on my homepage) accordingly. I have attached a more comprehensive test file,=20 using your prototype implementation at TeX level. best wishes Walter ------_=_NextPart_002_01C30DAC.EAB87900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: textcomp once more

On Mon, 28 Apr 2003 17:51:14 +0200, Lars Hellstr=F6m = wrote:

>>>font-loading packages contain explicit = declarations when
>>>they don't provide this default.
>>
>>This is not a general solution: [...]
>
>   = \UseTextSymbol{TS1}{\textmarried}
>
>would also work around the current subset = declaration mechanism. It's not
>an absolute stopper,

ACK.

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

Ok, forget my suggestion.


> [re. faking the Euro]
>>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.

That's what I meant.

>[...]
>I think I can write the MTX code.

TIA! 
I'll be happy to update the VFs in the PSNFSS = collection
(and those on my homepage) accordingly.

I have attached a more comprehensive test file, =
using your prototype implementation at TeX = level.


best wishes
Walter

------_=_NextPart_002_01C30DAC.EAB87900-- ------_=_NextPart_001_01C30DAC.EAB87900 Content-Type: application/octet-stream; name="fakeeuro.tex" Content-Transfer-Encoding: base64 Content-Description: fakeeuro.tex Content-Disposition: attachment; filename="fakeeuro.tex" XGRvY3VtZW50Y2xhc3NbYTRwYXBlcl17YXJ0aWNsZX0KXHBhZ2VzdHlsZXtlbXB0eX1ccGFyaW5k ZW50PTBwdAoKXHVzZXBhY2thZ2V7Y291cmllcixldXJvc3ltfQpcdXNlcGFja2FnZVtUMV17Zm9u dGVuY30KClxuZXdjb21tYW5ke1xmYWtlZXVyb31bMV1bXHNjcmlwdHNpemVdeyUKICAgXGxlYXZl dm1vZGUKICAgXHZhbGlnbnsjI1xjcgogICAgICBcdmZpbFxoYm94IHRvIDAuMDdlbXsjMT1caHNz fVx2ZmlsXGNyCiAgICAgIFxoYm94e0N9XGNyY3IKICAgfQp9CgpcbmV3Y29tbWFuZFx0ZXN0WzFd eyUKICBcdGV4dHR0eyMxOn1ccXVhZAogIFxmb250ZmFtaWx5eyMxfVxzZWxlY3Rmb250CiAgNzVc LFxmYWtlZXVybwogIFx0ZXh0aXR7NzVcLFxmYWtlZXVyb30KICB7XGJmc2VyaWVzCiAgNzVcLFxm YWtlZXVybwogIFx0ZXh0aXR7NzVcLFxmYWtlZXVyb30KICBccGFyfQp9CgpcYmVnaW57ZG9jdW1l bnR9CgolIG9wdGlvbmFsbHkgdHJ5IFxnZW5ldXJvIGZyb20gZXVyb3N5bS5zdHkKJSBcbGV0XGZh a2VldXJvPVxnZW5ldXJvCgolIGxldCdzIHRyeSBvdCB0aGUgQmFzZTM1IGZvbnRzLCBDaGFydGVy LCBVdG9waWEsCiUgVVJXIEdyb3Rlc3EsIFVSVyBBbnRpcXVhLgolIChQYWxhdGlubyBpcyBhbHJl YWR5IHRha2luZyBpdHMgRXVybyBmcm9tIHRoZSAKJSBQYXpvIGZvbnRzLikKClx0ZXN0e3B0bX0K XHRlc3R7cGh2fQpcdGVzdHtwY3J9Clx0ZXN0e2JjaH0KXHRlc3R7cHV0fQpcZW5ke2RvY3VtZW50 fQoKXHRlc3R7cGFnfQpcdGVzdHtwbmN9Clx0ZXN0e3Bia30KXHRlc3R7cHpjfQpcdGVzdHt1Z3F9 Clx0ZXN0e3VhcX0KXGVuZHtkb2N1bWVudH0KCgo= ------_=_NextPart_001_01C30DAC.EAB87900--