Alexey Melnikov wrote:
Philip Guenther wrote:
On Mon, 5 Feb 2007, Ken Murchison wrote:
Alexey Melnikov wrote:
...
I actually have a problem with *numbers* being case-insensitive. Cyrus
Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
So I would like to poll the WG regarding this issue. Do people want
to make to make number case-insensitive, or should this change be
undone?
(In the latter case there is one example in 3028bis-10 which uses
lowercase 'k' now, which has to change)
Obviously, digits are case-insensitive, but by stating "number" this
also includes QUANTIFIER, which only allows uppercase per the ABNF.
Nope. RFC 3028 said:
QUANTIFIER = "K" / "M" / "G"
Literal strings in ABNF are always case-insensitive.
Ok, you are right. But many people got beaten by this ABNF "feature".
Including CMU (before my time). Its about a 10 sec fix for me, so I'll
do whatever the consensus dictates.
--
Kenneth Murchison
Project Cyrus Developer/Maintainer
Carnegie Mellon University