On Wed, 18 Oct 2006, Kjetil Torgrim Homme wrote:
...
we have three proposals here:
$%<hex>
I dislike this as too specialized.
${hex:<hex>}
and a slightly more nebulous "a more unique prefix", perhaps this
qualifies:
$[hex:<hex>]
that would be fine with me, in any case.
I think these are both acceptable; I have a slight preference for ${}
As for the name of the extension, I think it should be "encoded-character"
instead of "quoted-character": this is not a quoting scheme but rather an
encoding scheme.
Regarding the description of the language in section 2.1, how does the
following addition (based on text from Alexey) look:
While this specification permits arbitrary octets to appear in
sieve scripts inside strings and comments, this has made it
difficult to robustly handle sieve scripts in user interfaces.
The "encoded-character" capability (section 2.4.2.4) provides an
alternative means of representing such octets in strings using
just US-ASCII characters. As such, the use of non-UTF-8 text in
scripts should be considered a deprecated feature that may be
abandoned.
That would be inserted as the third paragraph in that section and given
additional indentation (ala the behaviors described in section 2.7.2).
Philip Guenther