From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: issue importing metadata from PDF
Date: Fri, 12 Nov 2021 18:53:45 +0100 [thread overview]
Message-ID: <e44714bf-23ed-a3ef-2a04-f6a3fe1b1da2@gmx.es> (raw)
Hans,
I have a PDF document (which I didn’t generate) and it contains the
following objects:
1 0 obj
<<
/Title 272 0 R
/Producer 273 0 R
/Creator 274 0 R
/CreationDate 275 0 R
/ModDate 275 0 R
>>
endobj
272 0 obj
(This is an important title)
endobj
273 0 obj
(Mac OS X 10.12.1 Quartz PDFContext)
endobj
274 0 obj
(Keynote)
endobj
275 0 obj
(D:20161108071428Z00'00')
endobj
I cannot import these objects, since they are tables instead of strings,
after checking that with:
\startluacode
function document.transfer_metadata(name)
local main_doc = lpdf.epdf.load(name)
context(type(main_doc.Info.ModDate))
context(type(main_doc.Info.Title))
end
\stopluacode
Would it be possible that LMTX can deal with these objects and import
them as strings?
Many thanks for your help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2021-11-12 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 17:53 Pablo Rodriguez via ntg-context [this message]
2021-11-12 18:14 ` Hans Hagen via ntg-context
2021-11-12 18:24 ` Pablo Rodriguez via ntg-context
2021-11-12 19:04 ` Hans Hagen via ntg-context
2021-11-12 19:31 ` Pablo Rodriguez via ntg-context
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e44714bf-23ed-a3ef-2a04-f6a3fe1b1da2@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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.
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 NNTP newsgroup(s).