From: Max Nikulin <manikulin@gmail.com>
To: AW <alexander.willand@t-online.de>, emacs-orgmode@gnu.org
Subject: Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword
Date: Sun, 1 Oct 2023 23:02:38 +0700 [thread overview]
Message-ID: <a113634f-60e1-a4ae-fd20-c4e254095dae@gmail.com> (raw)
In-Reply-To: <2240064.iZASKD2KPV@linux.fritz.box>
On 28/09/2023 22:36, AW wrote:
>
> The idea to have a LATEX_PRE_HEADER to insert `\DocumentMetadata{}` is exactly
> what you need right now, if you export from orgmode to current LaTeX. With
> `\DocumentMetadata{}` you can add most of the necessary xmp data -- and I
> write most, because I'm using it on a daily basis, but haven't checked if
> really everything is included yet.
The question is if Juan Manuel can use \DocumentMetadata instead of the
pdfx package in his workflow.
However there is a common part of \DocumentMetadata and .xmpdata usage.
Currently Org mode allows to specify a very limited subset of metadata
through keywords
#+language: en
#+author: Me
#+title: Statement
The advantage is that the same data are used by all export backends:
LaTeX, HTML, etc. Specifying \DocumentMetadata literally without
substitutions from Org keywords may cause diverged values. That is why I
proposed to consider some kind of templates.
Another issue is extended metadata. I would consider an approach similar
to header arguments for source code blocks:
#+property: header-args :eval never-export
for all languages
#+property: header-args:elisp :exports both :eval yes
overrides for emacs-lisp
Perhaps it is not reasonable to require to specify all metadata through
Org keywords and it may be more convenient to combine raw LaTeX code and
fragments generated by Org
#+name: preamble
#+begin_src latex :exports none :noweb yes
\DocumentMetadata{
pdfstandard = a-2b
<<ox-latex-template-document-metadata-entries>>
}
<<ox-latex-template-documentclass>>
<<ox-latex-template-usepackage>>
#+end_src
Access to keywords values during evaluation of source code blocks have
to be implemented however.
next prev parent reply other threads:[~2023-10-01 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 18:00 [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword Juan Manuel Macías
2023-09-17 10:02 ` Ihor Radchenko
2023-09-17 17:23 ` Timothy
2023-09-18 8:09 ` Ihor Radchenko
2023-09-22 16:38 ` Max Nikulin
2023-09-24 18:42 ` Juan Manuel Macías
2023-09-25 13:58 ` Max Nikulin
2023-09-25 18:49 ` Juan Manuel Macías
2023-09-25 21:57 ` Thomas S. Dye
2023-09-26 15:39 ` Max Nikulin
2023-09-26 19:12 ` Juan Manuel Macías
2023-09-28 10:07 ` Max Nikulin
2023-09-28 12:31 ` Juan Manuel Macías
2023-09-29 2:38 ` Max Nikulin
2023-10-01 16:32 ` Max Nikulin
2023-09-28 15:36 ` AW
2023-10-01 16:02 ` Max Nikulin [this message]
2023-10-01 17:48 ` Juan Manuel Macías
2023-10-02 10:42 ` Max Nikulin
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=a113634f-60e1-a4ae-fd20-c4e254095dae@gmail.com \
--to=manikulin@gmail.com \
--cc=alexander.willand@t-online.de \
--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).