[Top] [All Lists]

Re: Proposal for escaping on non-UTF-8 sequences in Sieve

2006-09-18 08:23:59

Michael Haardt wrote:

On Sun, Sep 17, 2006 at 11:39:53PM +0100, Alexey Melnikov wrote:
Here is a strawman syntax for new quoted strings that would only allow
for valid UTF-8 sequences, but would also allow for escaped non-UTF-8

 new-quoted-string  = "~" DQUOTE new-quoted-text DQUOTE
You introduce a new lexical token to Sieve, thus changing the Sieve


I don't think the base spec allows that.

IMHO, if it explicitly prohibit such change, we need to change the base spec.

Sieve has a very
small syntax, moving most stuff to the semantical layer for being very
extensible, pretty much like LISP does.

The variables extension, for example, introduces the concept of expanding
strings, but only at the semantic level.  Syntactically, strings still
look the same.
The problem is that RFC 3028 said that '\ <octet>' for any <octet> other than <\> or <"> SHOULD be interpreted as <octet>. This effectively means that we can't fix quoted strings. So I had to introduced a new quoted string.

Do you have any better suggestions?