draft-ietf-nntpext-base-03.txt some comments
Martin J. Duerst
duerst at w3.org
Wed Jan 21 04:40:52 PST 1998
Stan Barber answered Paul Overell:
> > UTF-8-non-ascii = %xC0-FF 1*(%x80-BF) ; UTF-8 encoding of non-ASCII character
I hope you are aware of the fact that UTF-8 can be defined
more exactly. The above expression captures everything you
want to capture if you have only legal UTF-8, but won't
exclude erroneous sequences. Probably that's enough for
> > I have allowed any character to be escaped by a backslash, is this correct?
> > The text in 5. suggests that only [ * \ ? may be escaped.
> In the original wildmat, this was true. However with UTF-8, it may be necessary
> to extend the escape capability. Anyone have comments here?
You need escaping for those characters that do their work
defining the wildcard expressions. If [ * \ ? are the only
characters used for wildcard syntax, or if others can be
escaped otherwise (e.g. ]), you don't need to escape them.
As using non-ASCII characters in wildcard expressions would
mean that some people have difficulties using them, this
will probably never happen. So you don't need to escape them.
More information about the ietf-nntp