From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: PDF bookmarks - incorrect titles for registers
Date: Tue, 26 Nov 2013 20:30:03 +0100 [thread overview]
Message-ID: <41922.5335507237$1385494227@news.gmane.org> (raw)
In-Reply-To: <5294F248.1040001@wxs.nl>
On 2013-11-26 Hans Hagen wrote:
> 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?
>
> 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
>
> by default the title is set to a label which is not expandable
>
> the directive will convert the typeset title into a bookmark
>
Thanks for this detailed explanation. If I understand correctly, this switch
is intentional and won't be applied automatically even for registers or
other peculiar cases where title is specified differently/unexpectedly.
> > 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
Thanks, but this one is not so urgent.
Jan
___________________________________________________________________________________
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:30 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
2013-11-26 19:30 ` Jan Tosovsky [this message]
[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='41922.5335507237$1385494227@news.gmane.org' \
--to=j.tosovsky@email.cz \
--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).