From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Elston Subject: Re: Re: IMPORTANT: (possibly) incompatible Change Date: Sat, 10 Apr 2010 20:40:48 -0700 Message-ID: <4BC144C0.90105@comcast.net> References: <86sk7gooh2.fsf@portan.ibr.cs.tu-bs.de> <3E3E058D-6BBD-4D9B-845D-3E13235EF0DC@gmail.com> <4BB3973D.3090305@comcast.net> <9667B267-935B-4DFB-800B-FC76DBCCBF28@gmail.com> <8739z8g3ul.fsf@ara.blue-cable.net> <871ves8t5f.fsf@ara.blue-cable.net> <2D73D1C7-5BEF-46D2-9A56-4F4321005550@gmail.com> <87wrwk7cf7.fsf@ara.blue-cable.net> <6DA7F0F0-D60E-4214-889A-C5A135970E7B@tsdye.com> <6500482A-2E3D-4311-889B-77E33F82E72A@gmail.com> <87sk778yen.fsf@ara.blue-cable.net> <4BC0B5CB.1040108@comcast.net> <055203D9-970B-432D-92F8-2BE090DA7B98@tsdye.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O0o2i-0005Ku-OL for emacs-orgmode@gnu.org; Sat, 10 Apr 2010 23:41:04 -0400 Received: from [140.186.70.92] (port=59086 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O0o2d-0005Km-FI for emacs-orgmode@gnu.org; Sat, 10 Apr 2010 23:41:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O0o2b-0001Ho-S8 for emacs-orgmode@gnu.org; Sat, 10 Apr 2010 23:40:59 -0400 Received: from qmta15.emeryville.ca.mail.comcast.net ([76.96.27.228]:44934) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O0o2a-0001Hf-FL for emacs-orgmode@gnu.org; Sat, 10 Apr 2010 23:40:57 -0400 In-Reply-To: <055203D9-970B-432D-92F8-2BE090DA7B98@tsdye.com> 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: emacs-orgmode@gnu.org On 4/10/2010 1:01 PM, Thomas S. Dye wrote: > > On Apr 10, 2010, at 7:30 AM, Mark Elston wrote: > >> >> I am having problems with microtype, here. I don't know if it is >> happening in all my docs or just the ones I am working with now but >> pdf generation fails with the following in the log: >> >> ------------------------------------------------------------------ >> ... >> (Handouts07.out) (Handouts07.out) >> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\wasysym\uwasy.fd") >> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\ulasy.fd") >> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\umsa.fd") >> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\microtype\mt-msa.cfg") >> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\umsb.fd") >> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\microtype\mt-msb.cfg") >> [1{C:/Prog >> ramData/MiKTeX/2.7/pdftex/config/pdftex.map} >> ! pdfTeX error (font expansion): auto expansion is only possible with >> scalable >> fonts. >> \AtBegShi@Output ...ipout \box \AtBeginShipoutBox >> \fi \fi >> l.111 S >> harezer = Babylonian name, sharusur, ``protect the king.'' >> ! ==> Fatal error occurred, no output PDF file produced! >> Transcript written on Handouts07.log. >> ------------------------------------------------------------------ >> >> If I comment out the \usepackage{microtype} line then everything works >> fine. I am a casual user of latex so I don't really know what the >> comment above about scalable fonts is getting at. Perhaps I can set >> my docs up to do something different in terms of fonts to make this >> just work. >> >> Any ideas? >> >> Mark > > Hi Mark, > > Removing microtype is probably the easiest solution. It performs some > sophisticated micro-typographic adjustments that are typically found in > published material. The LaTeX world got on fine without them for years > and the casual LaTeX user can still do so. AFAIK, it is not necessary > for the Org-mode LaTeX exporter. > > All the best, > Tom > Tom, I did just that and haven't seen any noticeable degradation in quality. Thanks. Mark