Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f1HMa3f05914 for ; Sat, 17 Feb 2001 23:36:03 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1HMa3d20914 . for ; Sat, 17 Feb 2001 23:36:03 +0100 MIME-Version: 1.0 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1HMZwH01183 for ; Sat, 17 Feb 2001 23:35:58 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09932.02288B80" 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 XAA03031 for ; Sat, 17 Feb 2001 23:35:58 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 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 f1HMZuH01177 for ; Sat, 17 Feb 2001 23:35:56 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <14.D18A8019@mail.listserv.gmd.de>; Sat, 17 Feb 2001 23:35:47 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 489729 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sat, 17 Feb 2001 23:35:53 +0100 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 XAA27279 for ; Sat, 17 Feb 2001 23:35:52 +0100 (MET) 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 XAA21076 for ; Sat, 17 Feb 2001 23:35:52 +0100 Received: from postfix2-1.free.fr (postfix2-1.free.fr [213.228.0.9]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1HMZrx24320 for ; Sat, 17 Feb 2001 23:35:53 +0100 (MET) Received: from ujf-grenoble.fr (grenoble-53-24.dial.proxad.net [213.228.53.24]) by postfix2-1.free.fr (Postfix) with ESMTP id 5BE1DC0E0; Sat, 17 Feb 2001 23:35:50 +0100 (CET) References: <200102101651.f1AGpGi00601@smtp.wanadoo.es> <14983.4312.101767.632716@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: Mozilla 4.7 [fr] (WinNT; U) X-Accept-Language: fr,en,es Content-class: urn:content-classes:message Subject: Re: glyph collections viz font encodings Date: Sat, 17 Feb 2001 22:39:26 +0100 Message-ID: <3A8EEF8E.E4ED93B7@ujf-grenoble.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Thierry Bouche" 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: 3962 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09932.02288B80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach a =E9crit : > is there _anybody else_ who can come up with another reason why one = wants to > restrict a list of possible encodings (of the same font, or say set of > glyphs!) other than some of the actual fonts are not suitable for the = target > device, eg pdf output? well, no. I don't even agree that it's a good reason: make a virtual font with the glyphs you want in the required encoding. If the encoding was meant for your language, then you can probably enhance the typography. > however you are right, that there might be the problem that for some = fonts you > have TS1 available and for others you don't and you might want to mix = the > fonts. in the latter case things get more difficult. something harder: most of fonts declared as T are not fully compliant. most T1 tfms miss Ng, most TS1 miss \textmaried, etc. what can be done at latex level about that? declare numerous encodings (T1 from 8a, TS1 from 8a/8a+8x...) and find that most of the time asking for french+times will return that Times is not T1? > > > What happens if for some reason > > I like cyrillic times and latin palatino? > first of all that needs to be specifiable and that is an interesting = problem > in itself (though solvable in a decent way). It seems obvious to me that what you nedd here is a family whose T1 set points to palatino, and T2 to times. Latex requires standard markup to have portable & relatively independant content structure from font sets, etc. Customization should take place in the FD/VF rather than through packages. Or am I silly? > > And if there is no times font for cyrillic? Btw, also regarding persian, Bitstream cyberbit is a unicode font based on Times. Is it really impossible to have a Times-like font for any language? Th. ------_=_NextPart_001_01C09932.02288B80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: glyph collections viz font encodings

Frank Mittelbach a =E9crit :

> is there _anybody else_ who can come up with = another reason why one wants to
> restrict a list of possible encodings (of the = same font, or say set of
> glyphs!) other than some of the actual fonts are = not suitable for the target
> device, eg pdf output?

well, no. I don't even agree that it's a good reason: = make a virtual
font with the glyphs you want in the required = encoding. If the encoding
was meant for your language, then you can probably = enhance the
typography.


> however you are right, that there might be the = problem that for some fonts you
> have TS1 available and for others you don't and = you might want to mix the
> fonts. in the latter case things get more = difficult.

something harder: most of fonts declared as = T<something> are not fully
compliant. most T1 tfms miss Ng, most TS1 miss = \textmaried, etc. what
can be done at latex level about that? declare = numerous encodings (T1
from 8a, TS1 from 8a/8a+8x...) and find that most of = the time asking for
french+times will return that Times is not T1?


>
>  > What happens if for some = reason
>  > I like cyrillic times and latin = palatino?


> first of all that needs to be specifiable and = that is an interesting problem
> in itself (though solvable in a decent = way).

It seems obvious to me that what you nedd here is a = family whose T1 set
points to palatino, and T2 to times. Latex requires = standard markup to
have portable & relatively independant content = structure from font sets,
etc. Customization should take place in the FD/VF = rather than through
packages. Or am I silly?

>  > And if there is no times font for = cyrillic?


Btw, also regarding persian, Bitstream cyberbit is a = unicode font based
on Times. Is it really impossible to have a = Times-like font for any
language?

Th.

------_=_NextPart_001_01C09932.02288B80--