Mailing List Archive

New version of B59 uploaded: B59-include-bugs-2.txt
I've uploaded a new version of B59 which does not touch #config strings or
encode #echo strings. It fixes the following:

* Couldn't have \ in tag value strings.
* Couldn't have html entities in tag values, such as "
* #directive names were case sensitive
* tag names were case sensitive
* tag value strings should be delimited by " _or_ '
* did not allow whitespace around = in tag=value, or between -- and >

Remaining problems:

* Tag value strings should not need quoting if they don't contain special
characters, e.g. <--#echo var=PATH -->
* There should be an option to #echo to escape any html-active characters
in the echoed string.
* http_include wastes large strings holding names (tag & directive) and
values, which are limited to 72 and 1024 characters respectively, by the DTD.

David.
Re: New version of B59 uploaded: B59-include-bugs-2.txt [ In reply to ]
> I've uploaded a new version of B59 which does not touch #config strings or
> encode #echo strings. It fixes the following:
>
> Remaining problems:
>
> * Tag value strings should not need quoting if they don't contain special
> characters, e.g. <--#echo var=PATH -->

That might be regarded as a good thing. Better to use quotes everywhere
than have special cases. I'd vote to keep it this way unless there's
a good reason to change it.

> * There should be an option to #echo to escape any html-active characters
> in the echoed string.

define a new directive "#escape" which is the same as "#echo" with
the side-effect of escaping the results. ?
Re: New version of B59 uploaded: B59-include-bugs-2.txt [ In reply to ]
>> * Tag value strings should not need quoting if they don't contain special
>> characters, e.g. <--#echo var=PATH -->
>
>That might be regarded as a good thing. Better to use quotes everywhere
>than have special cases. I'd vote to keep it this way unless there's
>a good reason to change it.

The reason is to be compatible with standard HTML syntax. But it's hardly a
high priority.

>> * There should be an option to #echo to escape any html-active characters
>> in the echoed string.
>
>define a new directive "#escape" which is the same as "#echo" with
>the side-effect of escaping the results. ?

What I had in mind was <--#echo var="DOCUMENT_URI" escaped -->

David.