emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Emmanuel Charpentier <emanuel.charpentier@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.
Date: Thu, 29 Nov 2018 18:31:00 +0100	[thread overview]
Message-ID: <CAFG8T6X3HVo5eWAZfqJTjUbFea0M-+toxpx4mSPMko2tHhgjLA@mail.gmail.com> (raw)
In-Reply-To: <87tvk0q8op.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]

Dear Nicolas,

Thanks a lot for bearing with my nitpicking. A couple remarks below

Le jeudi 29 novembre 2018 à 15:07 +0100, Nicolas Goaziou a écrit :

> Hello,
>
> emanuel.charpentier@gmail.com writes:
>

> > AFAICT, polyglossia is to be preferred to babel for use with
> > xelatex or
> > lualatex. I'll see if this can be accomodated.

>
> What I mean is that you can also add compiler dependant packages in
> `org-latex-packages-alist'.


This is *not* *documented* (not even in the `org-latex-packages-alist''s
docstring).

I *checked* that one can add 4-element "cells" to this list (i. e. (list
argument package, snippet-flag, list-of-compilers)), but could not *guess*
it : I'm still running /H sapiens sapiens L./ v 1.0, no telepathic
interface, no oracular coprocessor. The only way would have been to read
the source code : not exactly the first reflex of the average end-user.

> No need to change the default package list.


I dispute that, since this "special configuration" is needed for LaTeX
export *only* , and *only* with non-English #+language:s. This
"exceptional" treatment should be handled silently by org-mode (as it does
with ODT, HTML and plain text export...). But see below.

> > > it should be ("AUTO" "babel" t).

> >
> > OK. That's much clearer. And does what is intended, BTW.
> >
> > Shouldn't that be default ?(No, I don't (yet) know *how* to do
> > that..).

>
> Babel is no small package.


Agreed. And polyglossia is worse...

> I think it would be a bit invasive as
> a default package.


Also agreed, with the reservation that "invasive" didn't mean the same
thing in the 1980s (when the core size of computers was measured in
kilobytes) and in the 2010s (the current core measurement unit is the
/giga/byte...).

> However, it is a good candidate for user-defined
> packages, i.e., `org-latex-packages-alist'.


Again, I think that the end user should *not* have to worry with this only
when exporting to LaTeX (or beamer or PDF). If this can be handled silently
when exporting to ODT, HTML or plain text, it should be handled silently
when exporting to LaTeX.

I do not know how to handle this. My *hunch* is that the Latex Export
function generating the preamble should check for language, and if not
default, add the relevant package(s) to the preamble. I'll need to dive in
the source code to be more precise (not anytime soon, though...).

> > Thus introducing a serious problem : exporting to text or ODT works
> > as
> > described, whereas export to latex needs (undocumented)
> > supplementary
> > steps.
> >
> > At the very minimum, this need for further config should be
> > mentioned
> > in the docs ; preferably, a default should be proposed.

>
> See above about the default. However, please feel free to suggest
> documentation improvements, however.


I'll propose a documentation attempt. But this should be considered as a
workaround, the real solution being the implementation of automatic
handling...

Cordially yours,

--
Emmanuel Charpentier


> Regards,
>




>
>

[-- Attachment #2: Type: text/html, Size: 14850 bytes --]

  reply	other threads:[~2018-11-29 17:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 20:36 Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored emanuel.charpentier
2018-11-27 14:20 ` Eric S Fraga
2018-11-27 15:29   ` Emmanuel Charpentier
2018-11-27 20:26     ` Nicolas Goaziou
2018-11-27 20:55       ` emanuel.charpentier
2018-11-27 23:40         ` Nicolas Goaziou
2018-11-28 11:38           ` Emmanuel Charpentier
2018-11-28 14:06             ` Nicolas Goaziou
2018-11-29  7:21               ` emanuel.charpentier
2018-11-29 14:07                 ` Nicolas Goaziou
2018-11-29 17:31                   ` Emmanuel Charpentier [this message]
2018-11-29 19:12                     ` Nicolas Goaziou
2018-12-02 20:26                       ` emanuel.charpentier
2018-12-05 16:37                         ` Emmanuel Charpentier
2018-12-06 22:40                         ` Nicolas Goaziou
  -- strict thread matches above, loose matches on Subject: below --
2018-11-25 18:01 emanuel.charpentier
2018-11-25 15:54 Emmanuel Charpentier
2018-11-25 19:03 ` Nicolas Goaziou
2018-11-25 20:32   ` Emmanuel Charpentier
2018-11-25 22:31     ` Nicolas Goaziou
2018-11-26  3:40       ` Emmanuel Charpentier
2018-11-26  8:58         ` Nicolas Goaziou
2018-11-25 21:33   ` Emmanuel Charpentier
2018-11-27 14:19 ` Michael Welle

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=CAFG8T6X3HVo5eWAZfqJTjUbFea0M-+toxpx4mSPMko2tHhgjLA@mail.gmail.com \
    --to=emanuel.charpentier@gmail.com \
    --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).