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 f1C7XjH13989 for ; Mon, 12 Feb 2001 08:33:45 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1C7Xid28189 . for ; Mon, 12 Feb 2001 08:33:44 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C094C6.21549280" 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 f1C7Xi716693 for ; Mon, 12 Feb 2001 08:33:44 +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 IAA00289 for ; Mon, 12 Feb 2001 08:33:43 +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 f1C7XhM06103 for ; Mon, 12 Feb 2001 08:33:43 +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 <5.F4BE2377@mail.listserv.gmd.de>; Mon, 12 Feb 2001 8:33:36 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487594 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 12 Feb 2001 08:33:40 +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 IAA00442 for ; Mon, 12 Feb 2001 08:33:39 +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 IAA09854 for ; Mon, 12 Feb 2001 08:33:39 +0100 Received: from Sina.sharif.ac.ir (sina.Sharif.AC.IR [194.225.40.9]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1C7XDu20953 for ; Mon, 12 Feb 2001 08:33:14 +0100 (MET) Received: from localhost (roozbeh@localhost) by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id LAA03610 for ; Mon, 12 Feb 2001 11:02:58 +0330 In-Reply-To: <14983.4312.101767.632716@istrati.zdv.uni-mainz.de> Return-Path: X-Sender: roozbeh@Sina.sharif.ac.ir Content-class: urn:content-classes:message Subject: Re: glyph collections viz font encodings Date: Mon, 12 Feb 2001 08:32:58 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Roozbeh Pournader" 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: 3837 This is a multi-part message in MIME format. ------_=_NextPart_001_01C094C6.21549280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sun, 11 Feb 2001, Frank Mittelbach wrote: > Anway, here we are now (still before midnight) ... I was found sleeping on my desk last night. I remember 2:30am, but your message in the mailbox has not been marked answered, I don't remember anything... > > 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 is not quite clear = which > atributes should be modified from language then. i guess the right = approach is > to consider all commands that are described on p173 of the LaTeX = Companion (eg > \famildefault ... \updefault) as language dependent commands but it is = kind of > tricky to find the right level for specification and behaviour Please note that with different scripts, we have different font classifications also. I'm not sure if the NFSS model is suitable for scripts other than Latin, Cyrillic, and Greek (ok, there are some others here, like Armenian). At least I should do some changes to the model to adapt to Persian. And this situation, when you want different font families for different scripts, is always the case with Persian. We = don't have anything named Times, or Helvetica, etc. We have our own families, which usually doesn't fit in the model. --roozbeh ------_=_NextPart_001_01C094C6.21549280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: glyph collections viz font encodings

On Sun, 11 Feb 2001, Frank Mittelbach wrote:

> Anway, here we are now (still before midnight) = ...

I was found sleeping on my desk last night. I remember = 2:30am, but your
message in the mailbox has not been marked answered, = I don't remember
anything...

>  > 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 = is not quite clear which
> atributes should be modified from language then. = i guess the right approach is
> to consider all commands that are described on = p173 of the LaTeX Companion (eg
> \famildefault ... \updefault) as language = dependent commands but it is kind of
> tricky to find the right level for specification = and behaviour

Please note that with different scripts, we have = different font
classifications also. I'm not sure if the NFSS model = is suitable for
scripts other than Latin, Cyrillic, and Greek (ok, = there are some others
here, like Armenian). At least I should do some = changes to the model to
adapt to Persian. And this situation, when you want = different font
families for different scripts, is always the case = with Persian. We don't
have anything named Times, or Helvetica, etc. We have = our own families,
which usually doesn't fit in the model.

--roozbeh

------_=_NextPart_001_01C094C6.21549280--