[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword
From: |
Juan Manuel Macías |
Subject: |
Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword |
Date: |
Thu, 28 Sep 2023 12:31:11 +0000 |
Max Nikulin writes:
> LaTeX code may be inserted
> - before \DocumentMetadata
> - between \DocumentMetadata and \documentclass
> - between \documentclass and preamble added by Org
> - between Org preamble and \begin{document}
The first two cases can be solved perfectly with LaTeX_pre_header,
without having to complicate your life further.
> Since ordering is important [...]
Starting with \documentclass, the order is important in certain cases
and not so important in others. And, anyway, you can always use a hook
like \AtBegin... \AtEnd..., etc.
And if users want to have complete control over the preamble (that is,
everything before \begin{document}), they can always define a new class
(in Org terminology) or write a preamble or a sty file in a separate Org
document using org-babel and literary programming. In a job I'm doing
now my preamble has 1736 lines. Writing it with org-babel is quite
comfortable. In short, I think (IMHO) Org already has enough resources
for those situations.
> I consider \begin{filecontents*}{\jobname.xmpdata} as an acceptable
> (but perhaps fragile) hack for LaTeX-first document. During export of
> Org file, this file should be written directly with values from Org
> metadata.
I think I should insist on what I said in my previous message, with a
copy/paste:
The thing is that here it is not a question of whether something can be
done in this way or in another better way. This is how a given package
recommends doing it. If the user wants to use that specific package, she/he
will have to follow these instructions. It's more. I am thinking, for
example, of the case in which the user has to obtain a * tex file, not a
PDF, because she/he is collaborating with more people who do not use
Org, but do use that code in the * tex document.
Apart from that, since any code (except \usepackage) is allowed before
\documentclass, I think that the user should have the possibility (and
the freedom) to enter in their *tex documents whatever they want in that
place, including comments, luacode, shebangs, etc.
--
Juan Manuel Macías
https://juanmanuelmacias.com
https://lunotipia.juanmanuelmacias.com
https://gnutas.juanmanuelmacias.com
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, (continued)
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Timothy, 2023/09/17
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Max Nikulin, 2023/09/22
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Juan Manuel Macías, 2023/09/24
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Max Nikulin, 2023/09/25
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Juan Manuel Macías, 2023/09/25
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Thomas S. Dye, 2023/09/25
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Max Nikulin, 2023/09/26
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Juan Manuel Macías, 2023/09/26
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Max Nikulin, 2023/09/28
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword,
Juan Manuel Macías <=
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, Max Nikulin, 2023/09/28
- Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword, AW, 2023/09/28