emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: AW <alexander.willand@t-online.de>
To: emacs-orgmode@gnu.org
Cc: Max Nikulin <manikulin@gmail.com>
Subject: Re: [patch] ox-latex.el: Add `LATEX_PRE_HEADER' keyword
Date: Thu, 28 Sep 2023 17:36:37 +0200	[thread overview]
Message-ID: <2240064.iZASKD2KPV@linux.fritz.box> (raw)
In-Reply-To: <uf3j9f$62n$1@ciao.gmane.io>

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

Am Donnerstag, 28. September 2023, 12:07:41 CEST schrieb Max Nikulin:
> More I read about .xmpdata, more it looks similar to an ugly kludge from
> my point of view.

Exporting from orgmode to LaTeX needs a high level approach: don't do 
complicated things, just use the appropriate LaTeX API. 

Unfortunately adding XMP metadata is the largest construction site in the 
LaTeX world: https://tug.org/TUGboat/tb43-3/tb135fischer-xmp.pdf 

The LaTeX Project Team developed a new pdf management, see here: https://
ctan.org/pkg/pdfmanagement-testphase : 

"The new PDF management code offers backend-independent interfaces to central 
PDF dictionaries, tools to create annotations, form Xobjects, to embed files, 
and to handle PDF standards."

The most important command is `\DocumentMetadata{}` and it needs to be placed 
before `\ḑocumentclass{}`

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. 

-- 
Regards,
Alexander 

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2023-09-28 15:37 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 [this message]
2023-10-01 16:02                   ` Max Nikulin
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=2240064.iZASKD2KPV@linux.fritz.box \
    --to=alexander.willand@t-online.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    /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).