From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: "kauśika cittūr" <citturs@gmail.com>,
"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Cannot access Lua function
Date: Sat, 30 Oct 2021 17:46:15 +0200 [thread overview]
Message-ID: <b213b28a-09b9-2cba-3a3c-bdd4bd953c76@xs4all.nl> (raw)
In-Reply-To: <5509076.DvuYhMxLoT@sreeramtplt>
On 10/30/2021 2:29 PM, kauśika cittūr wrote:
> On Saturday, October 30, 2021 4:57:07 PM IST Hans Hagen wrote:
>> that function was only meant for internal (inter-lua-module
>> communication) usage (also because there are some expectations abotu
>> what is in there)
>>
>> what do you want change?
>
> Dear Hans,
>
> I want to (/used to) set the creator and producer in the following manner
>
> \startluacode
> local metadata = lpdf.getmetadata();
> metadata['producer']='IKTS-VTR';
> metadata['creator']='IKTS-VTR';
> \stopluacode
>
> I was not able to do this using \setupinteraction, which I use to setup the
> title, subtitle and author.
cf the pdf speca:
Creator: If the document was converted to PDF from another format,
the name of the PDF processor that created the original document from
which it was converted.
Producer: If the document was converted to PDF from another format,
the name of the PDF processor that converted it to PDF.
so changing that is kind of cheating.
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
-----------------------------------------------------------------
___________________________________________________________________________________
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 prev parent reply other threads:[~2021-10-30 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 6:25 kauśika cittūr via ntg-context
2021-10-30 11:27 ` Hans Hagen via ntg-context
2021-10-30 12:29 ` kauśika cittūr via ntg-context
2021-10-30 15:46 ` Hans Hagen via ntg-context [this message]
2021-10-31 4:35 ` kauśika cittūr via ntg-context
2021-10-31 9:13 ` Hans Hagen via ntg-context
2021-10-31 16:15 ` kauśika cittūr via ntg-context
2021-11-02 5:18 ` Aditya Mahajan 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=b213b28a-09b9-2cba-3a3c-bdd4bd953c76@xs4all.nl \
--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).