Re: BUG: <PROTECT> does not accept uppercase PASS parameters:

[Denis Barbier <nospam@thanx>]

On Mon, Jul 16, 2001 at 11:53:20PM +0200, Axel Beckert wrote:
> Hi!
> 
> Denis Barbier wrote:
> > On Mon, Jul 16, 2001 at 11:04:53PM +0200, Axel Beckert wrote:
> > > There is a little bug in WML: <PROTECT> does not accept uppercase PASS
> > > parameters:
> > But attributes are case sensitive, so there is no reason to have a
> > special behaviour for this one.
> 
> Couldn't find the position in the doceumentation (of mp4h(1) and
> wml(1)), where this is mentioned. But I found this in mp4h(1): "As
> with HTML, macro names are case insensitive." In HTML attribute names
> are case insensitive, too. (Exception: XHTML, but in XHTML, there are
> no upper case tags or attribute names at all, IIRC.)
> 
> And my uppercase test example knows nothing about case sensitivity:
> 
> Input:
> 1| <define-tag foo whitespace=delete>
> 2|   <preserve foo FOO>
> 3|   <set-var %attributes>
> 4| foo=<get-var foo>
> 5| FOO=<get-var FOO>
> 6|   <restore foo FOO>
> 7| </define-tag>
> 8|
> 9| <foo foo=bar FOO=baz>
> 
> Output:
> 1| foo=baz
> 2| FOO=baz
> 
> And BTW: Why should there be a difference between <protect pass=2> and
> <PROTECT PASS=2>?

Alright, I was lying, you could have trusted me without checking ;)
So indeed you are right, PASS attribute has to be case-insensitive.
Your patch will be applied, thanks.

-- 
Denis Barbier
WML Maintainer
______________________________________________________________________
Website META Language (WML)                www.engelschall.com/sw/wml/
Official Support Mailing List                   sw-wml@engelschall.com
Automated List Manager                       majordomo@engelschall.com