From: "kauśika cittūr via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <j.hagen@xs4all.nl>
Cc: "kauśika cittūr" <citturs@gmail.com>
Subject: Re: PDF metadata and pdfx keys
Date: Wed, 15 Sep 2021 18:24:46 +0530 [thread overview]
Message-ID: <1712704.y5EPX7NnnQ@sreeramtplt> (raw)
In-Reply-To: <99bca6b1-9bc6-c1a9-77ee-72c3aa95ff4d@xs4all.nl>
On Wednesday, September 15, 2021 6:07:09 PM IST Hans Hagen wrote:
> On 9/15/2021 1:27 PM, kauśika cittūr via ntg-context wrote:
> > On Wednesday, September 15, 2021 8:08:34 AM IST kauśika cittūr wrote:
> >> Dear all,
> >>
> >> In my documents I use
> >> \setupinteraction
> >>
> >> [
> >>
> >> author={AuthorName},
> >> title={MyTitle},
> >> subtitle={MySubtitle},
> >>
> >> ]
> >>
> >> to set the document metadata. I also use
> >> \startluacode
> >>
> >> local metadata = lpdf.getmetadata();
> >> metadata['producer']='author';
> >> metadata['creator']='author';
> >>
> >> \stopluacode
> >> to set the creator and producer. However, the document produced by
> >> ConTeXt
> >> still has the user defined keys (pdfx:) written in the metadata. I have
> >> gone through lpdf-xmp.lua, lpdf-ini.lua and back-ini.lua. Yet, I am not
> >> able to figure out how to prevent the pdfx: tags from being written.
> >>
> >> Is it possible to prevent them from being written? I prefer not to tamper
> >> with any of the ConTeXt distribution files. In this case, is there
> >> something I can do per-document to prevent these tags from being written?
> >>
> >> Please advise.
> >>
> >> Thanks,
> >> kauśika
> >
> > Dear all,
> >
> > I hope my query is clear. For example when I run the command
> > pdfinfo -meta
> > on the generated PDF output, there are several 'pdfx:' tags in the XML
> > output.
> >
> > I am grateful for any help in this regard.
>
> these run specific entries are 'hard coded' (as are those in fonts
> metadata)
>
> (you can of course run the file through a script that replaces what you
> don't want (for some reason) by spaces, as long as the bytes stay at the
> same place)
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
Dear Hans,
I understand now. Thanks for clarifying.
Best,
kauśika
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-09-15 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 2:38 kauśika cittūr via ntg-context
2021-09-15 11:27 ` kauśika cittūr via ntg-context
2021-09-15 12:37 ` Hans Hagen via ntg-context
2021-09-15 12:54 ` kauśika cittūr via ntg-context [this message]
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=1712704.y5EPX7NnnQ@sreeramtplt \
--to=ntg-context@ntg.nl \
--cc=citturs@gmail.com \
--cc=j.hagen@xs4all.nl \
/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).