From: Hans Hagen <pragma@wxs.nl>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: ROT13 and alike
Date: Mon, 19 Feb 2001 12:19:12 +0100 [thread overview]
Message-ID: <3.0.6.32.20010219121912.01800640@server-1> (raw)
In-Reply-To: <000001c099ab$fe257960$a3ccfea9@nuovo>
At 01:50 PM 2/18/01 +0100, Giuseppe Bilotta wrote:
>Taco Hoekwater wrote:
>
>> Here is a solution that is just a little bit more robust than
>> your one: it obeys spaces and is properly nested. It also allows
>> primitives in the input string (\par, for example); and \unexpanded
>> macros that dont have an argument.
>>
>> Note that this is a hacker's version: you can't use this to process
>> arbitrary text: macro's that expand into something and e.g. accents
>> won't work!
>>
>> In general, it is very hard to do this kind of stuff safely in TeX.
>> A verbatim module would probably be the best solution. OTOH, my
>> approach allows:
>>
>> \section{\ROT{A section}}
>>
>[snip code]
>
>Well, that's an extremely instructive example!
>
>I gave a look at the verbatim approach, and got to the
>attached files.
>
>They still don't handle accents etc; Hans, how to make
>a verbatim that obeys cs's?
They will if you have an encoding that makes char>127 active
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-02-19 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 18:15 Giuseppe Bilotta
2001-02-17 18:30 ` Taco Hoekwater
2001-02-18 12:50 ` Giuseppe Bilotta
2001-02-19 11:19 ` Hans Hagen [this message]
2001-02-19 10:20 ` Hans Hagen
2001-02-19 22:45 ` Giuseppe Bilotta
2001-02-20 11:29 ` Hans Hagen
2001-02-20 15:58 ` Giuseppe Bilotta
2001-03-12 20:37 ` Hans Hagen
2001-03-14 0:26 ` 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=3.0.6.32.20010219121912.01800640@server-1 \
--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).