From: Stuart Jansen <sjansen@gurulabs.com>
Subject: Re: literal escape strings in bookmarks
Date: Thu, 07 Jul 2005 10:29:08 -0600 [thread overview]
Message-ID: <1120753748.8987.8.camel@localhost.localdomain> (raw)
In-Reply-To: <42CCD714.6010509@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]
On Thu, 2005-07-07 at 09:17 +0200, Hans Hagen wrote:
> there some sanitizing mechanism, but i'm not sure if you wan that here; Why do
> you use the hard coded \char's? If you use the named access mechanisms they are
> normally handled ok in bookmarks
Mostly because I wasn't aware they existed. Your suggestion mostly
works. Unfortunately, I still have a problem with the braces. I'm doing
automated document generation, and I've had problems with stray spaces
finding their way into the document, so I've taken to always using
{\letterbar} or \letterunderscore{}. I suppose I might be able to solve
the problem instead with some creative post-processing, but it'd be
kinda tricky. Any simple solutions?
=====
\setupinteraction[state=start]
\starttext
\placebookmarks[chapter,section]
\chapter{test{\letterunderscore}chapter}
The underscore character needs to be escaped in certain situations.
\chapter{start\letterbar{}stop}
So does the pipe symbol.
\chapter{foo}
\section{bar}
How can I avoid literals escape strings in bookmarks?
\stoptext
=====
--
Stuart Jansen <sjansen@gurulabs.com>
Guru Labs, L.C.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-07-07 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 23:05 Stuart Jansen
2005-07-07 7:17 ` Hans Hagen
2005-07-07 16:29 ` Stuart Jansen [this message]
2005-07-07 21:00 ` Hans Hagen
2005-07-07 22:07 ` Stuart Jansen
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=1120753748.8987.8.camel@localhost.localdomain \
--to=sjansen@gurulabs.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).