Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v936)
References: <4805.1257677519@cl.cam.ac.uk>
Content-Transfer-Encoding: 8bit
Message-ID:  <B63835D9-84E4-4BAF-A9D4-B15EDDB40AA0@gmail.com>
Date:         Sun, 8 Nov 2009 23:43:52 +1030
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: Please don't \RequirePackage{lmodern}
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4805.1257677519@cl.cam.ac.uk>
Precedence: list
Status: R

On 08/11/2009, at 9:21 PM, Robin Fairbairns wrote:

> Will Robertson <wspr81@GMAIL.COM> wrote:
>
>> On 08/11/2009, at 3:30 AM, Lars Hellström wrote:
>>
>>> Well, I think the T1 encoding default EC fonts beat both (at least
>>> if we restrict ourselves to the latin script; certainly part of the
>>> size of CM-Super is due to providing glyphs from other scripts as
>>> well, and these days drivers tend to subset fonts anyway).
>>
>> I didn't think there were PostScript Type 1 EC fonts?
>
> there aren't -- just this enormous monolithic lump called cm-super.

Exactly, and loading T1 *without* lmodern results in transparently  
swapping in these fonts, at least in every TeX distribution since  
early this decade or thereabouts. So it *is* T1 that I object to, in  
this context.

On the other hand, I'd far prefer having CM-Super embedded in all  
those legacy documents lying around on the web that use the bitmap EC  
fonts in PDF documents. Of course, I'm aware that for many years there  
simply weren't PostScript versions of the CM fonts freely available.  
Before LM, CM-Super was the best of a not-very-optimal situation.

-- Will