From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: PDF bookmarks - incorrect titles for registers
Date: Tue, 26 Nov 2013 20:11:04 +0100 [thread overview]
Message-ID: <5294F248.1040001@wxs.nl> (raw)
In-Reply-To: <005201ceeada$39d53fd0$ad7fbf70$@tosovsky@email.cz>
On 11/26/2013 8:03 PM, Jan Tosovsky wrote:
> On 2013-11-18 Jan Tosovsky wrote:
>>
>> when I specify custom titles for my registers, they are ignored in
>> bookmarks:
>>
>> \setupinteraction[state=start]
>> \placebookmarks[chapter]
>> \setupinteractionscreen[option=bookmark]
>>
>> \defineregister[indexname][indexnames]
>> \defineregister[indexsubject][indexsubjects]
>> \setupheadtext[indexname=Name Index]
>> \setupheadtext[indexsubject=Subject Index]
>>
>> \starttext
>> \completecontent
>> \chapter{Chapter}text\indexname{primary}\indexsubject{primary}
>> \startbackmatter
>> \completeindexname
>> \completeindexsubject
>> \stopbackmatter
>> \stoptext
>>
>> Is it necessary to switch something else on?
>
> According to the proposed solution at
> http://tracker.luatex.org/view.php?id=865
>
> it can be switched on using this magic formula
> \enabledirectives[references.bookmarks.preroll]
>
> What is the correct usage of this? And are there any details why it is
> required and what exactly it does?
by default the title is set to a label which is not expandable
the directive will convert the typeset title into a bookmark
> When it is added to the beginning of my example, it returns an error:
> attempt to call field 'boxtostring' (a nil value)
ah, only in my experimental tree, i'll add it to the beta
> But to be honest, I'd expect setting this flag internally by default as I
> cannot imagine any use case where the index ID should be preferred in favor
> of the title...
as titles can be anything and bookmarks are limited, we need to have
some protection in place ... unexpandable macros are simply dropped so
\labeltext{index} becomes index
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-11-26 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00f801cee49e$c9521ad0$5bf65070$@tosovsky@email.cz>
2013-11-26 19:03 ` Jan Tosovsky
[not found] ` <005201ceeada$39d53fd0$ad7fbf70$@tosovsky@email.cz>
2013-11-26 19:11 ` Hans Hagen [this message]
2013-11-26 19:30 ` Jan Tosovsky
[not found] ` <005401ceeadd$e83e6bc0$b8bb4340$@tosovsky@email.cz>
2013-11-26 22:13 ` Hans Hagen
2013-11-26 22:23 ` Hans Hagen
2013-11-18 20:43 Jan Tosovsky
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=5294F248.1040001@wxs.nl \
--to=pragma@wxs.nl \
--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).