emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: emacs-orgmode@gnu.org
Subject: Re: Re: IMPORTANT: (possibly) incompatible Change
Date: Sat, 10 Apr 2010 20:40:48 -0700	[thread overview]
Message-ID: <4BC144C0.90105@comcast.net> (raw)
In-Reply-To: <055203D9-970B-432D-92F8-2BE090DA7B98@tsdye.com>

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

  reply	other threads:[~2010-04-11  3:41 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 22:24 IMPORTANT: (possibly) incompatible Change Carsten Dominik
2010-03-31  9:00 ` Chris Gray
2010-03-31 12:35   ` Carsten Dominik
2010-03-31 14:16     ` Eric Schulte
2010-03-31 14:18       ` Carsten Dominik
2010-03-31 18:41     ` Mark Elston
2010-04-01  6:59       ` Carsten Dominik
2010-04-01 11:13         ` Carsten Dominik
2010-04-01 16:17           ` Thomas S. Dye
2010-04-01 16:51             ` Carsten Dominik
2010-04-02 16:25               ` Thomas S. Dye
2010-04-02  1:17         ` Mark Elston
2010-04-02  7:55           ` Carsten Dominik
2010-04-03 18:49             ` Mark Elston
2010-04-03 22:50               ` Henri-Paul Indiogine
2010-04-03 22:55                 ` Carsten Dominik
     [not found]                   ` <87pr2gezp9.fsf@belvoir.org>
     [not found]                     ` <A3285E87-A435-4CD9-B5BF-13330A09CE63@gmail.com>
2010-04-04 17:36                       ` Henri-Paul Indiogine
2010-04-04 19:44                         ` Mark Elston
2010-04-06 11:57                   ` Karsten Heymann
2010-04-06 14:53                     ` Carsten Dominik
2010-04-03 22:57               ` Carsten Dominik
2010-04-03 23:25                 ` Mark Elston
2010-04-04  0:14                   ` Carsten Dominik
2010-04-04  5:47                     ` Nick Dokos
2010-04-04  6:39                       ` Carsten Dominik
2010-04-06 12:30         ` Karsten Heymann
2010-04-06 14:53           ` Carsten Dominik
2010-04-06 16:03             ` Karsten Heymann
2010-04-06 16:23               ` Carsten Dominik
2010-04-06 16:50                 ` Karsten Heymann
2010-04-06 18:30                   ` Robert Klein
2010-04-06 18:48                     ` Thomas S. Dye
2010-04-07  7:37                       ` Carsten Dominik
2010-04-07  8:22                         ` Karsten Heymann
2010-04-07  8:47                           ` Carsten Dominik
2010-04-07 10:31                             ` Karsten Heymann
2010-04-07 15:51                               ` Thomas S. Dye
2010-04-07 16:00                                 ` Carsten Dominik
2010-04-10 17:30                           ` Mark Elston
2010-04-10 20:01                             ` Thomas S. Dye
2010-04-11  3:40                               ` Mark Elston [this message]
2010-04-07  8:16                       ` Karsten Heymann
2010-04-07  7:38                     ` Carsten Dominik
2010-04-07  9:15                   ` Ulf Stegemann
2010-04-07 10:30                     ` Karsten Heymann
2010-04-07 11:58                       ` Ulf Stegemann
2010-04-07 12:24                         ` Karsten Heymann
2010-04-02  1:29 ` [PATCH] " Eric Schulte
2010-04-02  2:47   ` Mark Elston
2010-04-02  5:38   ` Carsten Dominik
2010-04-03 16:20 ` Henri-Paul Indiogine
2010-04-03 16:55   ` Carsten Dominik
2010-04-03 17:19     ` Xiao-Yong Jin
2010-04-06 10:25       ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BC144C0.90105@comcast.net \
    --to=m_elston@comcast.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).