[Date Index][Thread Index]
[Date Prev][Date Next][Thread Prev][Thread Next]

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


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:

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>
9| <foo foo=bar FOO=baz>

1| foo=baz
2| FOO=baz

And BTW: Why should there be a difference between <protect pass=2> and

		Regards, Axel
Axel Beckert - abe@cs.uni-sb.de - http://abe.home.pages.de/
Student of Computer Science, University of Saarland (Germany)
Artificial Intelligence Laboratory (AI Lab), Prof. Dr. W. Wahlster;
WWW-/FTP-Administrator IBFI Schloß Dagstuhl; Students Representative CS
Website META Language (WML)                www.engelschall.com/sw/wml/
Official Support Mailing List                   sw-wml@engelschall.com
Automated List Manager                       majordomo@engelschall.com