ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: bookmark expansion again
Date: Mon, 27 May 2019 20:33:46 +0200	[thread overview]
Message-ID: <44309ae1-ac24-8593-5a4c-bf6c73738fdb@gmx.es> (raw)

Hi Hans,

I have the following sample:

    \def\eap{expansion}
    \def\MyContent{Expanded \eap}
    %~ \enabledirectives[references.bookmarks.preroll]
    \setupinteraction[state=start, title={\MyContent}]
    \placebookmarks[section]
    \starttext
    \section{\MyContent}
    \startsection[title=\MyContent, bookmark=\MyContent]
    \stopsection
    \stoptext

I see that now PDF contents are prerolled by default (which I think it
is a great idea [I hope it isn’t a bug]).

But bookmarks alone (when aren’t prerolled. From strc-sec.mkiv, I see
that prerolling is only applied to \currentstructuretitle when
\currentstructurebookmark is empty.

Would it be possible that \currentstructurebookmark could have
prerolling when it is different from \currentstructuretitle?

Sorry for insisting, but I need this to avoid having "main:345{/h2}" as
bookmark for some chapters.

Many thanks for your help,

Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2019-05-27 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 18:33 Pablo Rodriguez [this message]
2019-05-27 18:46 ` Wolfgang Schuster
2019-05-28 19:15   ` Pablo Rodriguez

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=44309ae1-ac24-8593-5a4c-bf6c73738fdb@gmx.es \
    --to=oinos@gmx.es \
    --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).