From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[2]: bookmarks
Date: Mon, 4 Feb 2002 12:58:31 +0100 [thread overview]
Message-ID: <1427686646.20020204125831@bigfoot.com> (raw)
In-Reply-To: <5.1.0.14.1.20020204121650.038830f8@server-1>
Monday, February 04, 2002 Hans Hagen wrote:
HH> At 03:24 PM 2/3/2002 +0100, Giuseppe Bilotta wrote:
>>HH> [alternatively you can do things like
>>
>>HH> \appendtoks\def\mycs{WHOW}\to\everysanitize
>>
>>HH> to get your own clean up in bookmarks]
>>
>>This solution doesn't seem to work (either because \everysanitize
>>is not issued by the PDF bookmark sanitizer or because it does not
>>become effective soon enough). I found that a possible alternative
>>is
HH> hm, before i look into it someone should make me a minimal test file (never
HH> use bookmarks myself)
\setupinteraction[state=start]
\placebookmarks[chapter]
\def\thisisatest{This is a test}
\starttext
\chapter{\thisisatest}
\stoptext
>>\immediate\writeutility{%
>> c \string\def\string\mycs{whatever we want}%
>>}
HH> that is a real terrible hack, isn't it?
Yes. I propose some form of "generic (PDF) sanitizer"
which gets called before the placebookmarks but can be configured
anywhere in the TeX source (and thus needs to be saved to the
auxiliary file). Something like:
\startPDFsanity
commandname {expansion in PDF form}
anothercommandname {another expansion}
andsoon {and so forth}
\stopPDFsanity
You could even define sanitizer as a class and then have PDF
sanitizers, PS sanitizers etc, all with a common interface like
the above.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2002-02-04 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201312002.VAA20337@smail.let.uu.nl>
2002-02-01 9:11 ` bookmarks Hans Hagen
2002-02-03 14:24 ` bookmarks Giuseppe Bilotta
2002-02-04 11:18 ` bookmarks Hans Hagen
2002-02-04 11:58 ` Giuseppe Bilotta [this message]
2002-02-04 18:57 ` Re[2]: bookmarks Berend de Boer
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=1427686646.20020204125831@bigfoot.com \
--to=bourbaki@bigfoot.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).