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 f1AGpeH08518 for ; Sat, 10 Feb 2001 17:51:40 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1AGpWd22147 . for ; Sat, 10 Feb 2001 17:51:40 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09381.BD28B600" Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1AGpQ704031 for ; Sat, 10 Feb 2001 17:51:31 +0100 (MET) 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 RAA21289 for ; Sat, 10 Feb 2001 17:51:25 +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 f1AGpNM21488 for ; Sat, 10 Feb 2001 17:51:23 +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 <6.8829C307@mail.listserv.gmd.de>; Sat, 10 Feb 2001 17:51:17 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487640 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sat, 10 Feb 2001 17:51:19 +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 RAA10280 for ; Sat, 10 Feb 2001 17:51:18 +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 RAA44368 for ; Sat, 10 Feb 2001 17:51:19 +0100 Received: from smtp.wanadoo.es (m1smtpisp03.wanadoo.es [62.36.220.63] (may be forged)) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1AGpKu15021 for ; Sat, 10 Feb 2001 17:51:20 +0100 (MET) Received: from [62.36.81.105] (usuario2-36-81-105.dialup.uni2.es [62.36.81.105]) by smtp.wanadoo.es (8.10.2/8.10.2) with ESMTP id f1AGpGi00601 for ; Sat, 10 Feb 2001 17:51:16 +0100 (MET) Return-Path: X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Content-class: urn:content-classes:message Subject: Re: glyph collections viz font encodings Date: Sat, 10 Feb 2001 17:46:05 +0100 Message-ID: <200102101651.f1AGpGi00601@smtp.wanadoo.es> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Javier Bezos" 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: 3792 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09381.BD28B600 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Sorry for this late answer. > it seems to me that this all boils down to "i want to ensure that all = is > Type1" so that i get proper pdf files. or am i wrong? That could be a possible reason, but very likely some people could find other reasons. But yes, that is what I was thinking about. More generally, the automatic selection should be done taking into account possible restrictions/features defined by the user. (Which restrictions/features can be set is to be studied.) It should be noted, however, that text also contains symbols and that usually we are using _two_ encodings -- if we say \defaultencoding{T1}, \textdagger is taken from cmsy, which is the default symbol font (OMS). So we have another problem when selecting an encoding -- in fact we must select two. Instead of multilingual documents, I would rather speak of multiscript documents, since imo this concept is more important. Of course, = different languages use the latin script in different ways, but when there are languages using diffent scripts there are additional problems. For example, in a text containing both latin and cyrillic scripts the following line of code might not make sense: \usepackage{times} \usepackage{textcomp} Is times applied to both scripts? What happens if for some reason I like cyrillic times and latin palatino? Which symbol fonts are used? And if there is no times font for cyrillic? Or there is no symbol font? If you use latin with tibetan, things are more complicated because tibetan doesn't understand what a times font is, and again, what happens if a certain script requires two or more metrics and/or encodings? Finally, it remains the problem of what happens if people dislike the default settings. But that is unavoidable... Javier ___________________________________________________________ Javier Bezos | TeX y tipografia jbezos at wanadoo dot es | http://perso.wanadoo.es/jbezos/ ........................................................... CervanTeX http://apolo.us.es/CervanTeX/CervanTeX.html ------_=_NextPart_001_01C09381.BD28B600 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: glyph collections viz font encodings

Hi all,

Sorry for this late answer.

> it seems to me that this all boils down to = "i want to ensure that all is
> Type1" so that i get proper pdf files. or = am i wrong?

That could be a possible reason, but very likely some = people could
find other reasons. But yes, that is what I was = thinking about.
More generally, the automatic selection should be = done taking
into account possible restrictions/features defined = by the user.
(Which restrictions/features can be set is to be = studied.)

It should be noted, however, that text also contains = symbols and that
usually we are using _two_ encodings -- if we say = \defaultencoding{T1},
\textdagger is taken from cmsy, which is the default = symbol font (OMS).
So we have another problem when selecting an encoding = -- in fact
we must select two.

Instead of multilingual documents, I would rather = speak of multiscript
documents, since imo this concept is more important. = Of course, different
languages use the latin script in different ways, but = when there are
languages using diffent scripts there are additional = problems. For
example, in a text containing both latin and cyrillic = scripts the
following line of code might not make sense:

\usepackage{times}
\usepackage{textcomp}

Is times applied to both scripts? What happens if for = some reason
I like cyrillic times and latin palatino? Which = symbol fonts are used?
And if there is no times font for cyrillic? Or there = is no symbol
font? If you use latin with tibetan, things are more = complicated
because tibetan doesn't understand what a times font = is, and again,
what happens if a certain script requires two or more = metrics and/or
encodings?

Finally, it remains the problem of what happens if = people dislike
the default settings. But that is = unavoidable...

Javier
___________________________________________________________
Javier = Bezos           &n= bsp;  | TeX y tipografia
jbezos at wanadoo dot es  | http://perso.wanadoo.es/jbezos/<= /A>
...........................................................
CervanTeX   http://apolo.us.es/C= ervanTeX/CervanTeX.html

------_=_NextPart_001_01C09381.BD28B600--