ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Giuseppe Bilotta" <oblomov@freemail.it>
Subject: Re: ROT13 and alike
Date: Sun, 18 Feb 2001 13:50:26 +0100	[thread overview]
Message-ID: <000001c099ab$fe257960$a3ccfea9@nuovo> (raw)
In-Reply-To: <3A8EC33F.3DB883D3@quicknet.nl>

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

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?

Giuseppe Bilotta

Using Microsoft products is like 
having sex without condoms---but
much less pleasurable

[-- Attachment #2: g-rot.zip --]
[-- Type: application/x-zip-compressed, Size: 1525 bytes --]

  reply	other threads:[~2001-02-18 12:50 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 [this message]
2001-02-19 11:19     ` Hans Hagen
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='000001c099ab$fe257960$a3ccfea9@nuovo' \
    --to=oblomov@freemail.it \
    /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).