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 f15NQCH03964 for ; Tue, 6 Feb 2001 00:26:12 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f15NQBd02398 . for ; Tue, 6 Feb 2001 00:26:11 +0100 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 f15NQBM04581 for ; Tue, 6 Feb 2001 00:26:11 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C08FCB.06B48200" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id AAA20484 for ; Tue, 6 Feb 2001 00:26:10 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f15NQA712006 for ; Tue, 6 Feb 2001 00:26:10 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <14.DB40C063@mail.listserv.gmd.de>; Tue, 6 Feb 2001 0:26:05 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487403 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 6 Feb 2001 00:26:07 +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 AAA21562 for ; Tue, 6 Feb 2001 00:26:06 +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 AAA121750 for ; Tue, 6 Feb 2001 00:26:06 +0100 Received: from venus.open.ac.uk (venus.open.ac.uk [137.108.143.2]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f15NQ5u26048 for ; Tue, 6 Feb 2001 00:26:05 +0100 (MET) Received: from fell.open.ac.uk by venus.open.ac.uk via SMTP Local (Mailer 3.1) with ESMTP; Mon, 5 Feb 2001 23:26:03 +0000 Received: (from car2@localhost) by fell.open.ac.uk (8.9.3+Sun/8.9.1) id XAA16090; Mon, 5 Feb 2001 23:26:17 GMT In-Reply-To: References: Return-Path: X-Mailer: VM 6.76 under Emacs 20.7.1 X-Authentication-Warning: fell.open.ac.uk: car2 set sender to car2@fell.open.ac.uk using -f Content-class: urn:content-classes:message Subject: Re: glyph collections viz font encodings Date: Tue, 6 Feb 2001 00:26:16 +0100 Message-ID: <14975.13976.503037.872425@fell.open.ac.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Chris Rowley" 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: 3708 This is a multi-part message in MIME format. ------_=_NextPart_001_01C08FCB.06B48200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Javier > > [Chris]-- differences in the metrics (these can cause major differences in > > the typesetting). > > Yes, differences in the metrics, which can reshape the whole document. Oh dear, yes! This does rather mess-up fine typesetting. My feeling is that since the fonts available are going to get more and more diverse (if only very slowly) the robust medium-term solution for a TeX-like typesetting engine is to add the ability to bundle the font-metrics with the document (possibly virtually when network font warehouses really exist). This is analogical to putting the glyph information into a ps or pdf form of a document. chris ------_=_NextPart_001_01C08FCB.06B48200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: glyph collections viz font encodings

Javier

> > [Chris]-- differences in the metrics (these = can cause major
differences in
> > the typesetting).
>
> Yes, differences in the metrics, which can = reshape the whole document.

Oh dear, yes!  This does rather mess-up fine = typesetting.

My feeling is that since the fonts available are going = to get more and
more diverse (if only very slowly) the robust = medium-term solution for
a TeX-like typesetting engine is to add the ability = to bundle the
font-metrics with the document (possibly virtually = when network font
warehouses really exist).

This is analogical to putting the glyph information = into a ps or pdf
form of a document.


chris

------_=_NextPart_001_01C08FCB.06B48200--