From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: Expansion in PDF metadata
Date: Fri, 4 Mar 2016 11:52:04 +0100 [thread overview]
Message-ID: <20160304115204.2fd81c1f@homerow> (raw)
In-Reply-To: <56D956B9.6090106@wxs.nl>
On Fri, 4 Mar 2016 10:34:49 +0100
Hans Hagen <pragma@wxs.nl> wrote:
> On 3/4/2016 7:58 AM, Marco Patzer wrote:
> > Hi!
> >
> > How to expand \translate so that it doesn't show up in the PDF
> > metadata? Example:
> >
> > \setupdocument [metadata:title=\documentvariable{title}]
> > \mainlanguage [sv]
> >
> > \startdocument [title={\translate[en=Foo, sv=Bar]}]
> > \input knuth
> > \stopdocument
> >
> > This literally shows:
> >
> > Title: \translate [en=Foo, sv=Bar]
> >
> > The following workaround does the job, but it's not that elegant:
> >
> > \setupdocument [metadata:title=\documentvariable{title}]
> > \enablemode [sv]
> >
> > \startmodeset
> > [en] {\mainlanguage[en]\startdocument[title=Foo]}
> > [sv] {\mainlanguage[sv]\startdocument[title=Bar]}
> > \stopmodeset
> >
> > \input knuth
> > \stopdocument
> >
> > Is there a better mechanism to support multiple languages in the
> > PDF metadata or just have \translate expanded?
>
> \mainlanguage[sv]
>
> \startmodeset
> [*en] {
> \setupdocument [metadata:title=Foo]
> }
> [*sv] {
> \setupdocument [metadata:title=Bar]
> }
> [default] {
> \setupdocument [metadata:title=Far]
> }
> \stopmodeset
>
> \startdocument [title={\translate[en=Foo, sv=Bar]}]
> \input knuth
> \stopdocument
That works and seems cleaner, thanks.
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-03-04 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 6:58 Marco Patzer
2016-03-04 9:34 ` Hans Hagen
2016-03-04 10:52 ` Marco Patzer [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=20160304115204.2fd81c1f@homerow \
--to=lists@homerow.info \
--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).