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 f18BsuH30220 for ; Thu, 8 Feb 2001 12:54:56 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f18Bstd13133 . for ; Thu, 8 Feb 2001 12:54:55 +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 f18Bst726589 for ; Thu, 8 Feb 2001 12:54:55 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C091C5.F4526800" 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 MAA16565 for ; Thu, 8 Feb 2001 12:54:54 +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 f18Bsq726583 for ; Thu, 8 Feb 2001 12:54:52 +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 <4.C79D3A1D@mail.listserv.gmd.de>; Thu, 8 Feb 2001 12:54:47 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 488132 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 8 Feb 2001 12:54:49 +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 MAA17109 for ; Thu, 8 Feb 2001 12:54:48 +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 MAA18794 for ; Thu, 8 Feb 2001 12:54:49 +0100 Received: from server-10.tower-4.starlabs.net (mail.london-1.starlabs.net [212.125.75.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f18Bsmu15866 for ; Thu, 8 Feb 2001 12:54:48 +0100 (MET) Received: (qmail 13084 invoked from network); 8 Feb 2001 11:52:22 -0000 Received: from nagmx1e.nag.co.uk (HELO nag.co.uk) (62.232.54.130) by server-10.tower-4.starlabs.net with SMTP; 8 Feb 2001 11:52:22 -0000 Received: from penguin.nag.co.uk (IDENT:root@penguin.nag.co.uk [192.156.217.14]) by nag.co.uk (8.9.3/8.9.3) with ESMTP id LAA15766 for ; Thu, 8 Feb 2001 11:54:40 GMT Received: by penguin.nag.co.uk (8.9.3) id LAA01175; Thu, 8 Feb 2001 11:54:41 GMT In-Reply-To: <14978.31798.631846.935627@mira.idris.fr> (gaulle@IDRIS.FR) References: <14978.31798.631846.935627@mira.idris.fr> Return-Path: X-VirusChecked: Checked Content-class: urn:content-classes:message Subject: Re: default inputenc/fontenc tight to language Date: Thu, 8 Feb 2001 12:54:41 +0100 Message-ID: <200102081154.LAA01175@penguin.nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" 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: 3748 This is a multi-part message in MIME format. ------_=_NextPart_001_01C091C5.F4526800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I still use OT1 for French and will continue until new fonts appear in public domain with the same quality as CM fonts for the 128-255 range. --bg With mltex presumably? Using standard TeX isn't this exactly equivalent to using a VF based re-encoding of the cm fonts such as ae fonts? You get the benefits of T1 encoding for hyphenation, so long as you don't require any of the extra glyphs that were added to T1. This is a reasonable solution to the "freely available T1 cm fonts" problem in many cases (It's what I use in the MathML spec which uses T1 encoded times mainly but ae version of cmtt for monospaced) David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet = delivered through the MessageLabs Virus Control Centre. For further information = visit http://www.star.net.uk/stats.asp ------_=_NextPart_001_01C091C5.F4526800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: default inputenc/fontenc tight to language

   I still use OT1 for French and will = continue until new fonts
   appear in public domain with the same = quality as CM fonts for
   the 128-255 range.

     --bg


With mltex presumably? Using standard TeX isn't this = exactly equivalent
to using a VF based re-encoding of the cm fonts such = as ae fonts?
You get the benefits of T1 encoding for hyphenation, = so long as you
don't require any of the extra glyphs that were added = to T1.
This is a reasonable solution to the "freely = available T1 cm fonts"
problem in many cases (It's what I use in the MathML = spec which uses
T1 encoded times mainly but ae version of cmtt for = monospaced)

David

________________________________________________________________= _____
This message has been checked for all known viruses = by Star Internet delivered
through the MessageLabs Virus Control Centre. For = further information visit
http://www.star.net.uk/stats.as= p

------_=_NextPart_001_01C091C5.F4526800--