From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX markup in \setupinteraction for PDF metadata fields
Date: Sun, 17 Jan 2016 19:27:31 +0100 [thread overview]
Message-ID: <569BDD13.3020306@gmail.com> (raw)
In-Reply-To: <CAA36g0WAFWg=Goqwn=67uFk5Lx8JJBNPqdQTtSwfwAP9OK=OvA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]
> Kate F <mailto:kate@elide.org>
> 17. Januar 2016 um 18:53
> On 17 January 2016 at 17:00, Wolfgang Schuster
>
> I don't know, actually. In this case these are values which remain
> constant throughout the document. So all I'm after here is a mechanism
> for storing variables by name. Is there something more appropriate to
> use for those kind of variables?
You can use the \setvariables command the set the values and access them
with \getvariables:
\setvariables
[information]
[title=Document title,
author=Author name]
\setupinteraction
[ state=start,
title=\getvariable{information}{title},
author=\getvariable{information}{title}]
\starttext
\unknown
\stoptext
There is also the \setupdocument command (a simple wrapper for the
\setvariables command)
which uses predefined keywords to set fields in the pdf file. You can
access the values from
\setupdocument command in your document with \documentvariable{<KEY>}.
\setupdocument
[ metadata:title=Document title,
metadata:author=Author name]
\setupinteraction[state=start]
\starttext
\unknown
\stoptext
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2323 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-17 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 16:56 Kate F
2016-01-17 17:00 ` Wolfgang Schuster
2016-01-17 17:53 ` Kate F
2016-01-17 18:27 ` Wolfgang Schuster [this message]
2016-01-17 18:55 ` Alan BRASLAU
2016-01-17 19:09 ` Wolfgang Schuster
2016-01-17 22:39 ` Alan BRASLAU
2016-01-17 22:43 ` Wolfgang Schuster
2016-01-17 19:48 ` Kate F
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=569BDD13.3020306@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=ntg-context@ntg.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).