From: Marcin Borkowski <mbork@mbork.pl>
To: emacs-orgmode@gnu.org
Subject: Re: ox-latex: default packages cleaning
Date: Wed, 15 Jul 2015 00:16:30 +0200 [thread overview]
Message-ID: <87si8qmlkx.fsf@mbork.pl> (raw)
In-Reply-To: <87r3ok589c.fsf@gmx.us>
On 2015-07-07, at 16:53, Rasmus <rasmus@gmx.us> wrote:
> Hi,
Hi,
and sorry for my delay – I have a huge email backlog...
> We could do some cleaning of org-default-package-alist before Org 8.3.
Yes, yes, yes!
> * tolerance
>
> Why is "\\tolerance=1000" part of org-default-package-alist? Is this
> value good for all languages? If we keep it, it should be configurable.
> But people who explicitly wants this behavior can probably add it
> themselves.
>
> If it's a means to archive "high-quality" paragraphs, maybe microtype is
> probably the 'proper' fix...
My suggestion: forget about \tolerance. It’s low-level TeX stuff,
hardly anybody knows what it does, really (it is one of the dozen or two
parameters governing the line-breaking algorithm), and most people would
not see any difference anyway. I wouldn’t add microtype, OTOH. One
reason: it issues a lot of warnings when you use a font it does not
know. It doesn’t hurt, but some people don’t like warnings. Also, some
people might not really /want/ microtype – it messes around with font
widths, and even with the default settings (which are rather
conservative), it can look a bit strange.
> * Fixltx2e
>
> This packages is depreciated with TL2015 cf. LaTeX News 22. We can use
> \RequirePackage[current]{latexrelease} but there's no point in that....
> AFAIK latexrelease only useful for backwards compatibility.
Didn’t even know that.
> * marvosym¹
> * Wasysym²
My opinion: remove both.
> Rasmus
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
prev parent reply other threads:[~2015-07-14 22:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 14:53 ox-latex: default packages cleaning Rasmus
2015-07-07 15:48 ` Eric S Fraga
2015-07-07 19:35 ` Suvayu Ali
2015-07-07 20:05 ` Rasmus
2015-07-07 20:52 ` Suvayu Ali
2015-07-07 21:07 ` Rasmus
2015-07-08 12:53 ` Rasmus
2015-07-08 13:43 ` Suvayu Ali
2015-07-08 13:53 ` Rasmus
2015-07-08 14:09 ` Suvayu Ali
2015-07-08 14:26 ` Rasmus
2015-07-08 14:55 ` Suvayu Ali
2015-07-08 15:41 ` Suvayu Ali
2015-07-08 16:06 ` Rasmus
2015-07-08 18:35 ` Rasmus
2015-07-16 8:29 ` Suvayu Ali
2015-07-16 8:49 ` Rasmus
2015-07-27 8:22 ` Sebastien Vauban
2015-07-27 8:30 ` Rasmus
2015-07-27 9:22 ` Sebastien Vauban
2015-07-27 9:31 ` Rasmus
2015-07-29 16:21 ` Rasmus
2015-07-08 12:54 ` Rasmus
2015-07-08 13:44 ` Suvayu Ali
2015-07-14 22:31 ` Marcin Borkowski
2015-07-15 8:33 ` Rasmus
2015-07-10 11:25 ` Robert Klein
2015-07-11 10:48 ` Rasmus
2015-07-11 18:53 ` Robert Klein
2015-07-13 10:08 ` Rasmus
2015-07-14 22:16 ` Marcin Borkowski [this message]
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=87si8qmlkx.fsf@mbork.pl \
--to=mbork@mbork.pl \
--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).