ietf-mta-filters
[Top] [All Lists]

Re: Sieve base-spec revision I-D

2005-02-22 11:26:26

On Wed, Feb 16, 2005 at 05:36:26AM +0100, Kjetil Torgrim Homme wrote:
there is a slight problem since a header can use encoding to include NUL
and other problematic characters, and the Sieve interpreter undoes this
in order to present it all as UTF-8 or plain octets to the user.  I wish
there were an escape for including octets by value in strings, e.g.
"\x00".  that would be an incompatible change, can we do that?

(if so, I'd want "\uXXXX" and "\UXXXXXXXX" for Unicode, too (same syntax
as Java and C99))

I agree with wanting to be able to specify octets by value.  I'd hate to
do it with a leading alpha character though, as '\x' is supposed to mean
'x'.  I've done it a la C escapes, with '\0nnn' meaning an octal value,
where you only have to make '0' special, and I don't think \0 sequences
being special would come as as much of a shock as \<alpha> sequences
being special.  I could also see a \0<alpha> sequence having extra
meaning, e.g. '\0xnn' for hex.  

What would be the need for \uXXXX that a series of multiple escaped
bytes couldn't provide?

mm


<Prev in Thread] Current Thread [Next in Thread>