From: John B. <joh...@ne...> - 2002-01-11 09:29:41
|
> 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 ;-) Isn't that the problem? The qdstrings are allowed to contain all the seperation characters in any combination they like. How then to detect the end of the qdstring? > > I don't see how it is possible at all, without defining an additional > > escape mechanism or list of disallowed characters (the previous approach). > My first idea was not only to check for allowed characters but to check for > those special words defined in RFC 2252 (DESC, MUST, MAY, ..) > But I was to lazy to do it that way ;-)) And those special words may also exist inside a qdstring. I am sure that we can define a reasonable approach by adding restrictions on qdstrings. However, I am really missing something if there is a way of parsing this 'as is'. regards, jb |