From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Forbidden things in bookmarks
Date: Fri, 21 Apr 2006 00:55:02 +0200 [thread overview]
Message-ID: <44481146.5010808@wxs.nl> (raw)
In-Reply-To: <ops8bv8ae79niby6@localhost>
nico wrote:
> On Fri, 21 Apr 2006 00:25:00 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>
>> nico wrote:
>>
>>> Hello,
>>>
>>> The heading bookmarks don't accept some macros, like \copyright.
>>>
>>> In latex there's a handy feature that allows to define the text to put
>>> in
>>> the TOC and the text in the heading itself, like \chapter[Title in the
>>> TOC]{Actual Title in the doc}. Is it possible to do it in context? If
>>> not,
>>> maybe it could be an interesting feature to add.
>>>
>>>
>> in context, \chapter[arg]{whatever} the arg is a (list of) references
>>
>> also, toc and bookmarks may differ
>>
>> you can add an \bookmark{alternative} after the \chapter command
>>
>
> Great.
>
>
>> even better is:
>>
>> \appendtoks
>> \def\copyright{(C)}%
>> \to \simplifiedcommands
>>
>> at the top of your file which replace the copyright by (C)
>>
>
> Ah, really powerfull. What is the rule that decides to use simplified
> commands instead of normal ones?
>
most characters will adapt but copyright is (when not available) a
composed char
simplified commands are used when one says \simplifycommands
Hans
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-04-20 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 20:55 nico
2006-04-20 22:25 ` Hans Hagen
2006-04-20 22:46 ` nico
2006-04-20 22:55 ` Hans Hagen [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=44481146.5010808@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).