From: Carsten Dominik <carsten.dominik@gmail.com>
To: Karsten Heymann <karsten.heymann@blue-cable.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: IMPORTANT: (possibly) incompatible Change
Date: Tue, 6 Apr 2010 18:23:21 +0200 [thread overview]
Message-ID: <2D73D1C7-5BEF-46D2-9A56-4F4321005550@gmail.com> (raw)
In-Reply-To: <871ves8t5f.fsf@ara.blue-cable.net>
On Apr 6, 2010, at 6:03 PM, Karsten Heymann wrote:
> Hi Carsten,
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>> On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
>>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>>> \usepackage[AUTO]{inputenc}
>>>> \usepackage[T1]{fontenc}
>>>> \usepackage{graphicx}
>>>> \usepackage{longtable}
>>>> \usepackage{float}
>>>> \usepackage{wrapfig}
>>>> \usepackage{soul}
>>>> \usepackage{latexsym}
>>>> \usepackage{amssymb}
>>>> \usepackage{hyperref}
>>
>> Do you have any recommendations for the sequence in which these
>> packages should be called? Or does that make no difference at all?
>> Does any of these cause problems if they are called twice (say I
>> add them, but users have them configured already?)
>
> The only critical one is hyperref, which should always be loaded last
> (see
> http://tug.ctan.org/tex-archive/macros/latex/contrib/hyperref/doc/manual.html#x1-30002)
> .
>
>> What is is really changing due to these last two
>> settings (microtype) and tolerance, could you explain in a bit more
>> detail?
>
> I will try to explain it in my own poor words. microtype activates
> advanced functions of the pdftex compiler (nowadays the standard TeX
> compiler used by all distributions) to perform various subtle output
> modifications, like shifting letters a tiny bit into the right
> margin so
> that the margin looks *visually* aligned. Also it stretches and pulls
> letters for tiny amounts so words fit better into paragraphs without
> standing into the margin.
>
> This is also the area where \tolerance takes action. It's a low level
> TeX directive that controls how much the whitespace between words may
> differ in width when typesetting a justified paragraph (I'm not sure
> what the correct translation of the German word "Blocksatz" is).
> It's a
> number in the range between 0 and 9999 (plus the special 10.000
> meaning
> infinite for TeX ;-) ). The standard value 200 is way much too
> perfectionist for normal day-to-day typesetting, especially when
> writing
> in languages where typical words are much longer then in English, like
> German for example. Normal Desktop Text processors always operate in
> "10.000"-Mode, meaning there's an infinite amount of whitespace
> allowed
> between words, with the result of possibly large holes between the
> words
> to keep the right margin aligned. TeX on the other hand will deny to
> typeset paragraphs when it cannot find a solution (for the full
> paragraph!) inside it's tolerance limits and write words into the
> right
> margin so the author can manually fix the situation (rephrase, fix
> hyphenation, ...). Tolerance values up to 2000 still look much better
> than anything from Word/OOo and reduce the need to manually correct
> these problems (and to explain this stuff to new users).
>
>> And: Can I expect fixltx2e to be present in all distributions?
>
> Yes, it's part of the latex base packages and thus always available
> (given any not really really ancient LaTeX installation, e.g. more
> than
> a decade).
>
>> Is \tolerance defined in microtype, or did you put these together
>> just
>> incidentally?
>
> They are completely independent.
Thanks a lot for all this, I will follow your advice.
One final question: Will any of these packages spoil the fun
for people who want to process through .dvi instead of directly to pdf?
>
>>> Karsten
>>
>> I really appreciate expert advice about this. Thank you.
>
> I'm more than glad my rusty LaTeX knowledge is of any use,
> especially to
> the awesome org-mode community (and it's even more awesome author). If
> you want advice from some *real* experts, ask in the comp.text.tex or
> the de.comp.text.tex newsgroup. That's a completely different level,
> I'm
> just some kind of semi-power-user that had too much time on
> university.
That is way more than I know about LaTeX/TeX internals, so fully
appropriate here. Yes, comp.text.tex and de.comp.text.tex, I used
to hang out there more while writing reftex.el and cdlatex.el, but
always more as a reader than as a contributor. I loved to read these
groups, that was always a high intensity place to be at.
Thanks again.
- Carsten
next prev parent reply other threads:[~2010-04-06 16:23 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 [this message]
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
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=2D73D1C7-5BEF-46D2-9A56-4F4321005550@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=karsten.heymann@blue-cable.net \
/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).