From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: New try at multi-lingual export to latex/pdf using pdflatex and babel
Date: Sun, 11 Feb 2024 11:04:56 +0000 [thread overview]
Message-ID: <875xyv1ctj.fsf@posteo.net> (raw)
In-Reply-To: <CAO48Bk-cH8p7oxGkJHnPzX2_JxEX5OVGxs=gTjYOjcYWsrNU6Q@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Sun, 11 Feb 2024 07:22:35 +0100")
Pedro Andres Aranda Gutierrez writes:
> I agree it does not take advantage of the AUTO facility here, but I
> nevertheless think it would
> be interesting to show people how to do this. Until we expand the AUTO
> facility to cope with
> all quirks of multi-language in pdflatex (lualatex and xetex are a
> different pair of shoes), a quick
> and dirty alternative may be helpful for people. The introductory text
> could be
Pedro, the only problem I see with that is that it is an example of
LaTeX rather than Org. The only Org part here is #+LaTeX_header, and in
the entire section it's already made clear enough what it's used for.
Perhaps a brief reminder (the AUTO facility of the previous examples
is very limited) could be added first, and that if the users want to
obtain more complex, or more specific results (like the case you
exemplify for pdfLaTeX) they must put explicit LaTeX code, using
LaTeX_header. And then your example would come, but emphasizing that the
LaTeX documentation must be consulted. wdyt?
My point is that if we abuse examples of this type (at the expense of
"#+latex_header:something"), or "how is this done in LaTeX?", in the end
a LaTeX manual is made instead of Org.
I'm glad you enjoyed the jump to LuaTeX. :-)
Best regards,
Juan Manuel
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
next prev parent reply other threads:[~2024-02-11 11:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 8:44 New try at multi-lingual export to latex/pdf using pdflatex and babel Pedro Andres Aranda Gutierrez
2024-01-21 13:02 ` Ihor Radchenko
2024-01-21 17:11 ` Pedro Andres Aranda Gutierrez
2024-01-21 17:47 ` Juan Manuel Macías
2024-01-22 6:30 ` Pedro Andres Aranda Gutierrez
2024-01-22 6:47 ` Pedro Andres Aranda Gutierrez
2024-01-22 13:11 ` Juan Manuel Macías
2024-01-22 12:10 ` Ihor Radchenko
2024-01-22 13:40 ` Juan Manuel Macías
2024-01-23 7:41 ` Pedro Andres Aranda Gutierrez
2024-01-24 16:25 ` Ihor Radchenko
2024-01-25 7:25 ` Pedro A. Aranda
2024-01-25 13:41 ` Ihor Radchenko
2024-01-25 16:54 ` Pedro A. Aranda
2024-01-26 13:28 ` Ihor Radchenko
2024-01-26 17:49 ` Pedro Andres Aranda Gutierrez
2024-01-28 13:47 ` Ihor Radchenko
2024-01-28 17:02 ` Pedro Andres Aranda Gutierrez
2024-01-29 13:28 ` Ihor Radchenko
2024-01-29 14:34 ` Pedro Andres Aranda Gutierrez
2024-01-29 14:51 ` Ihor Radchenko
2024-01-29 14:51 ` Pedro Andres Aranda Gutierrez
2024-02-09 23:10 ` Ihor Radchenko
2024-02-10 6:13 ` Pedro Andres Aranda Gutierrez
2024-02-10 14:39 ` Ihor Radchenko
2024-02-11 6:22 ` Pedro Andres Aranda Gutierrez
2024-02-11 11:04 ` Juan Manuel Macías [this message]
2024-04-15 12:21 ` Ihor Radchenko
2024-04-22 20:06 ` Ihor Radchenko
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=875xyv1ctj.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=paaguti@gmail.com \
--cc=yantar92@posteo.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).