From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: a bit offtopic, fonts in exported PDF documents - oops Date: Tue, 31 Aug 2010 08:31:42 +0200 Message-ID: <59985F38-8550-4357-86B1-4199F382BB30@gmail.com> References: <4C76A590.9050800@ccbr.umn.edu> <20100827074111.38ed3280.alantyree@gmail.com> <26419.1283179859@gamaville.dokosmarshall.org> <4C7BCA58.7070503@ccbr.umn.edu> <31733.1283183895@gamaville.dokosmarshall.org> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=59123 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OqKNs-00057M-Uv for emacs-orgmode@gnu.org; Tue, 31 Aug 2010 02:31:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OqKNq-0003wc-P7 for emacs-orgmode@gnu.org; Tue, 31 Aug 2010 02:31:52 -0400 Received: from paard.ic.uva.nl ([145.18.40.182]:49443) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OqKNq-0003wW-FQ for emacs-orgmode@gnu.org; Tue, 31 Aug 2010 02:31:50 -0400 In-Reply-To: <31733.1283183895@gamaville.dokosmarshall.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: nicholas.dokos@hp.com Cc: emacs-orgmode , Alan L Tyree On Aug 30, 2010, at 5:58 PM, Nick Dokos wrote: > Erik Iverson wrote: > >> That would be my thought, too. However, it appears that cm-super is >> only "suggested" by texlive-fonts-extra, so in general >> will not get installed with that package, unless you ask for >> suggested packages also. (This is all Debian/Ubuntu by the way). >> > > Right. I was wrong about texlive-fonts-extra: you need to install the > cm-super package to get the cm-super fonts. I am investigating the > various fonts right now and will update the org-dependencies.org =20 > file on > Worg later on this week. We can also add a FAQ entry to point back to > org-dependencies - that should take care of the documentation changes, > right? > >> Both this system and MikTeX >> offer cm-super as a standalone package, so perhaps just recommending >> that package (cm-super) would suffice? I confirmed that cm-super is >> not one of the default MikTeX packages in a standard install, so >> Windows users may benefit from this advice, too. > > Do windows users use evince? I'd think they mostly go with Acrobat =20 > Reader, > in which case they should have no problems with Type3 fonts. > >>> The other possible change that Erik identified is the deletion of =20= >>> the >>> t1enc package from the list of packages that org includes in =20 >>> exported >>> LaTeX by default. I haven't tried without it, but it does indeed =20 >>> seem to >>> be an obsolete remnant of times long past. >> >> I have tried without it. I was unable to to see any differences =20 >> between >> using \usepackage[T1]{fontenc} and adding the \usepackage{t1enc} >> line. This makes sense given the FAQ answer below. >> > > So getting rid of the \usepackage{t1enc} in org sounds like the right > thing to do (but including it does not hurt, so there is no urgency, > iiuc.) OK, thanks to all of you - I have removed the t1enc entry now. - Carsten > > Nick > >> The TeX FAQ >>> (http://www.tex.ac.uk/cgi-bin/texfaq2html?label=3Dt1enc ) says: >>> >>> ,---- >>> | Why use fontenc rather than t1enc? >>> | | In the very earliest days of LaTeX2e, the only way to use the T1 >>> | encoding was t1enc; with the summer 1994 =93production=94 release, = the >>> | fontenc package appeared, and provided comprehensive support for =20= >>> use of >>> | the encoding. >>> | | Nevertheless, the t1enc package remains (as part of the LaTeX >>> 2.09 >>> | compatibility code), but it does very little: it merely selects =20= >>> font >>> | encoding T1, and leaves to the user the business of generating the >>> | character codes required. >>> | | Generating such character codes could be a simple matter, if the >>> T1 >>> | encoding matched any widely-supported encoding standard, since =20 >>> in that >>> | case, one might expect one=92s keyboard to generate the character >>> | codes. However, the T1 encoding is a mix of several standard =20 >>> encodings, >>> | and includes code points in areas of the table which standard =20 >>> encodings >>> | specifically exclude, so no T1 keyboards have been (or ever will =20= >>> be) >>> | manufactured. >>> | | By contrast, the fontenc package generates the T1 code points >>> from >>> | ordinary LaTeX commands (e.g., it generates the =E9 character =20 >>> codepoint >>> | from the command \=92e). So, unless you have program-generated T1 =20= >>> input, >>> | use \usepackage[T1]{fontenc} rather than \usepackage{t1enc}. >>> `---- >>> >>> Nick >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Please use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> - Carsten