ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Subject: Sectioning. PDF bookmarks.
Date: Thu, 8 Nov 2001 18:37:08 +0100	[thread overview]
Message-ID: <1510835268.20011108183708@bigfoot.com> (raw)

Hello,

this is a another area where ConTeXt needs refining. As far as I
know, ConTeXt only allows peculiar section names to be handled via
the \nolist command:

\chapter{Section name \nolist{with a part that does not go in the
TOC}}.

But consider that there are cases where the 'short' form is deeply
different from the long one. And there is another important issue,
which is PDF bookmarks, in which a lot of commands have to be
redefined to display properly (e.g. \dots has to be turned into
three dots).

I propose a structure like

\chapter[full] {Full name}
        [short]{Short name}
        [pdf]  {PDF bookmark name}

Second point, more tightly related to PDF bookmarking, is the
opportunity of a way to define how commands are to be interpreted
in bookmarks.

Say for example that I have a ConTeXt document where I define

\definesynonyms[abbreviation][abbreviations][\infull]
\setupsynonyms[abbreviation][textstyle=\smallcaps]
\abbreviation[RPG]{rpg}{Role Playing Game}

This gives me a command \RPG that I can use throughout my document
to display rpg (in small caps, because this is the style I use for
abbreviation, and here again we get back to the problem of \sc
having to turn lowercase into uppercase when small caps are not
active). But if I have a title like

\chapter{Pregnancy in \RPG s}

I want this to display as

Pregnancy in RPGs

in the bookmarks. Instead, what I get is an 'undefined command
sequence'. How to deal with it?

--
Giuseppe "Oblomov" Bilotta


             reply	other threads:[~2001-11-08 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 17:37 Giuseppe Bilotta [this message]
2001-11-20  8:50 ` Hans Hagen
2001-11-20  9:35   ` Re[2]: " Giuseppe Bilotta

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=1510835268.20011108183708@bigfoot.com \
    --to=bourbaki@bigfoot.com \
    /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).