From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: ox-latex: default packages cleaning
Date: Wed, 15 Jul 2015 10:33:26 +0200 [thread overview]
Message-ID: <87r3o9lt0p.fsf@gmx.us> (raw)
In-Reply-To: 87r3oamkvc.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
>> I would also suggest removing inputenc. At the moment, it is loaded
>> with the AUTO option. AFAIK, this is redundant since most recent
>> (meaning for quite a few years) TeX engines already use the encoding of
>> the file if nothing is specified.
>
> Can you elaborate on that? AFAIK, XeTeX and LuaTeX use UTF-8 by
> default, but pdfetex (which is the default LaTeX engine) does not. And
> quite a lot of people ose pdfetex (me included;-)). I haven't heard
> about any heuristic determination of encoding by TeX (and I hope nothing
> like that happens, since it could be disastrous).
At least on Windows/Miktex this isn't working. And while I don't like
miktex enough people do.
>> The next one would be fontenc, now it is loaded with T1. I'm not sure
>> if this is needed. Maybe LaTeX experts like Marcin or Fabrice could
>> comment.
>
> Thanks for calling me an expert, though I'm not one regarding fonts and
> their encodings;-).
>
> With fontenc, the thing is tricky. I do not know much about other
> languages, but you actually can't use LaTeX to typeset texts in Polish
> without changing the default LaTeX's font encoding (which is OT1, and it
> doesn't support some Polish letters). (Usually, I do not use fontenc
> for that, since there is a specialized package for Polish typesetting.)
>
> I guess that removing fontenc for non-English texts might lead to
> erroneous results – at least in case of presence of certain Polish words
> (e.g., some names in bibliographies). I guess we don’t want that.
>
> OTOH, one thing we /might/ want to add is \usepackage{lmodern}. The
> Latin Modern family of fonts is a drop-in replacement for the default
> Computer Modern, but with all sorts of accented characters. Using this
> font family has the advantage that accented characters are not build
> from letters and accents, but are single glyphs in the font. AFAIR,
> this makes words containing accented letters hyphenatable. Not a huge
> gain, but sometimes may be important (especially in some languages, and
> with narrow columns).
If people have the need for additional fonts they can add it. In a patch
further down the thread I add support to set backends for packages (so
fontenc is only loaded if using pdflatex).
If you'd replaced lmodern with libertine I would have been more inclined
to agree (though it might not have as wide support as LM). BTW: I guess
any of the GUST fonts would have pretty great glyph support.
An easy mechanism for changing font package is nice. E.g. I use libertine
by default, but in some cases I'd might want to use another package in
which case I'd want to have libertine replaced.
>> We could also take this opportunity to provide users an easy way to
>> switch between TeX engines.
>
> I second that!
Feel free to test the patch in another post. If's difficult because: (i)
we want to be able to change engines with some liberty, but not to much
(e.g. you can run xelatex but you can't run myrandomscript.sh); (ii) the
info plist is not available at compile time so we have to write the info
to file, in the patch I use the AUCTeX latex-command var; (iii) it would
be nice to support flags (-shell-escape), but see (i).
Rasmus
--
I hear there's rumors on the, uh, Internets. . .
next prev parent reply other threads:[~2015-07-15 8:33 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 [this message]
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
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=87r3o9lt0p.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).