Re: schema format questions

[Peter M. <pet...@ma...>]

Hi,

On Thursday 10 January 2002 16:05, you wrote:
> > >   RFC2252 does not explicitely deny it. It simply gives the
> > >   following definitions
> > >       dstring         =3D 1*utf8
> > >       qdstring        =3D whsp "'" dstring "'" whsp
> > >   without defining utf8 further
> > >   Since a single quote is a utf8 character, this could mean
> > >   that single quotes inside qdstrings are really allowed.
> Yep. But the question for me is whether ( and ) and whitespace are
> permitted (which they presumably are although I must confess to not hav=
ing
> checked utf8 :-) because that makes the whole thing technically unparsa=
ble
> unless I am missing something.
> ? How can you parse that sensibly? (Even in perl...)
>
> The '1*utf8' seems to make a nonsense of any possibility of parsing.

If you take "utf8" as the definition of a UTF8 encoded Unicode character,
parsing still stays possible (if it is impossible, it is for other reason=
s).
UTF8 encodes 7 bit ASCII to 7bit ASCII and any characters beyond \x7f
into a sequence of characters in the range [\x80-\xFF].

Since all separation characters used in RFC 2252 are 7bit ASCII,
parsing stays possible without having to think about those non-ASCII
characters (just let them where they are ;-)

> I don't see how it is possible at all, without defining an additional
> escape mechanism or list of disallowed characters (the previous approac=
h).
My first idea was not only to check for allowed characters but to check f=
or=20
those special words defined in RFC 2252 (DESC, MUST, MAY, ..)
But I was to lazy to do it that way ;-))

Yours
Peter

--=20
Peter Marschall     |   eMail: pet...@ma...
Scheffelstra=DFe 15   |          pet...@is...
97072 W=FCrzburg      |   Tel:   0931/14721
PGP:  D7 FF 20 FE E6 6B 31 74  D1 10 88 E0 3C FE 28 35