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

Re: [wml] Re: c) or d)

Yesterday you sent me mail regarding [wml] Re: c) or d):

*> > My preferred one is (d) (and to be honest i never thought of (a) before)
*> > because it prevents nesting problems, e.g.
*> >   <define-container bla>%body</define-container>
*> >   <bla><blb></bla></blb>
*> > is valid with (c).
*> Why should it be more or less valid in case c and/or d? If both are
*> containers, this line is simply incorrect. Either you start matching the
*> <bla> with the </bla> and notice that <blb> is not closed. Or you Start
*> with <bla>, recurse into <blb>...</blb> and notice that <bla> is never
*> closed.

the point here is about 'ignoring invalid syntax'. If you 'close
first' then the the parser sees <blb> but the </bla> is more
powerfull in closing ... and thus the parser irnores <blb> as
obviously not being the <blb></blb> pair it expected ... same goes
for the </blb> at the end which also gets ignored as being a lone
tag which does not make sens ...

I maintain that I think wml should parse all tags and the
definition for unknown tags is that they reinsert themselves ... 
In connection with xhtml it might be nice to be able to tell mp4h
to barf on lone <ddd> tags (they should be <ddd/>) ...

The only thing which we then need todo for 'magic' stuff where
part of the html tags get generated by perl is a simple 'mp4h quote
tag' which disables mp4h parsing for a stretch of text ... I know
that I can use <protect pass=2> for this but a simple tag pair like
<' '> would make it simpler .... 

 ______    __   _
/_  __/_  / /  (_) Oetiker, Timelord & SysMgr @ EE-Dept ETH-Zurich
 / // _ \/ _ \/ / TEL: +41(0)1-6325286  FAX:...1517  ICQ: 10419518 
/_/ \.__/_.__/_/ oetiker@ee.ethz.ch http://ee-staff.ethz.ch/~oetiker

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