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 f0V9oe716893 for ; Wed, 31 Jan 2001 10:50:40 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f0V9pS730950 . for ; Wed, 31 Jan 2001 10:51:28 +0100 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 f0V9od711236 for ; Wed, 31 Jan 2001 10:50:39 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C08B6B.44E51800" 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 KAA29471 for ; Wed, 31 Jan 2001 10:50:38 +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 f0V9ocM04495 for ; Wed, 31 Jan 2001 10:50:38 +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 <3.18B37143@mail.listserv.gmd.de>; Wed, 31 Jan 2001 10:50:32 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 485326 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 31 Jan 2001 10:50:32 +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 KAA15498 for ; Wed, 31 Jan 2001 10:50:30 +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 KAA29844 for ; Wed, 31 Jan 2001 10:50:30 +0100 Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f0V9oUp03035 for ; Wed, 31 Jan 2001 10:50:30 +0100 (MET) Received: from heraldgate2.oucs.ox.ac.uk ([163.1.2.50] helo=frontend2.herald.ox.ac.uk ident=exim) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #3) id 14NtuG-0000tb-00 for LATEX-L@urz.uni-heidelberg.de; Wed, 31 Jan 2001 09:50:28 +0000 Received: from spqr.oucs.ox.ac.uk ([163.1.15.17]) by frontend2.herald.ox.ac.uk with esmtp (Exim 2.02 #1) id 14NtuH-0007gj-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Wed, 31 Jan 2001 09:50:29 +0000 In-Reply-To: References: <14965.53535.903052.219374@istrati.zdv.uni-mainz.de> <14965.58948.408001.938171@spqr2.oucs.ox.ac.uk> <14967.7486.689372.23588@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: VM 6.86 under Emacs 20.7.2 Content-class: urn:content-classes:message Subject: Re: default font encoding Date: Wed, 31 Jan 2001 10:50:33 +0100 Message-ID: <14967.57321.160569.450294@spqr.oucs.ox.ac.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Sebastian Rahtz" 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: 3682 This is a multi-part message in MIME format. ------_=_NextPart_001_01C08B6B.44E51800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Vladimir Volovich writes: > the technology is based on auto-tracing high-resolution bitmaps -- > such as 20000 dpi (from gf files produced by metafont), then > optimizing and autohinting with fontlab. fine. but the experience of everyone else (Taco Hoekwater comes to mind) is that the final stage cleanup is far far more time consuming than you imply. > the resulting fonts look quite good (there are a few very small > glitches which could be seen with very high magnification). they may > need some hand work (which i will not be able to do due to the lack = of > time), but even without this i think that this could be better than > nothing (at least :). I think we have been here before. viz Basil Malyshev's Paradissa fonts, which were *nearly* right, but not quite. Sebastian ------_=_NextPart_001_01C08B6B.44E51800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: default font encoding

Vladimir Volovich writes:
 > the technology is based on auto-tracing = high-resolution bitmaps --
 > such as 20000 dpi (from gf files produced = by metafont), then
 > optimizing and autohinting with = fontlab.

fine. but the experience of everyone else (Taco = Hoekwater comes to
mind) is that the final stage cleanup is far far more = time consuming
than you imply.

 > the resulting fonts look quite good (there = are a few very small
 > glitches which could be seen with very = high magnification). they may
 > need some hand work (which i will not be = able to do due to the lack of
 > time), but even without this i think that = this could be better than
 > nothing (at least :).

I think we have been here before. viz Basil Malyshev's = Paradissa
fonts, which were *nearly* right, but not = quite.

Sebastian

------_=_NextPart_001_01C08B6B.44E51800--