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

Re: [wml] Re: [wml] e) or f) : unknown tags parsing

Today you sent me mail regarding [wml] Re: [wml] e) or f) : unknown tags...:

*> On Mon, May 29, 2000 at 05:37:14PM +0200, Denis Barbier wrote:
*> > So here are our choices:
*> >   e) Unknown tags are always simple.
*> >      Drawback: logical structure is not preserved, e.g.
*> >         <lang:en: <b>This is a test</b>>
*> >                has 4 attributes: <b>This, is, a, test</b>
*> >       
*> >   f) Trailing slash determines tag type.
*> >      Drawback: in some situations, HTML tags must be protected.
*> > 
*> > Could anyone evaluate pros and cons and send feedback?
*> I'd say e)
*> Why? 
*> - In most cases there is only one argument needed. In this cases we can
*>   (implictly) join all arguments and use them as arg1.

this is not the case in our setup ... we love multi argument
complex tags ...

*> - Some other cases could be changed (like <ifeq>) to use a simpler
*>   syntax, thus beeing no problem.
this is cosmetics ... the core must be clean ... 

*> - If there remain any cases, we should be able to solve this by some
*>   (simple?) quoting. <tag "<b>foo bar</b>" "<i>baz quux</i>">

well the quoating thing might also be a problem ... 

Our use of mp4h is mostly that we 

a) redifine existing HTML tags to produce something nice ... eg
   <H1>xxxx</H1> ends up as a gif with xxxx graphical contents 
   in the final page

b) we create complex tags like
   <LINK TITLE="Blabl" HREF="http://..">
   link description

The set of tags defined in a) may change at any moment ... so if
wml defies all unknown tags as simple this may lead to things
breaking badly when new tags are introduced. Which shadow existing
html tags.

So how about this:

In the old metahtml it was possible to protect a tag (maybe this
is still the case today) by putting a * into the tag name
<table*>....</table*> so how about requiering these starts to be
present in all tags which should be parsed as simple  tags and
never redefined by wml ... 

For Denis example this would look like this

<XXX></XXX> and <YYY></YYY> are complex tags

In a Navbar like environment we want to do something like this:


Using strict parsing this would not be allowed on the other hand if
we at some point redefine <TABLE> in wml everything will break.

So instead we require that the user marks table as NON parsable
simple tags by writing:


<TABLE> will now always remain <TABLE> in this context even if I
redefine the normal <TABLE> tag to have some other meaning eg to
work with layers or some other new technique ...

As for the xhtml parsing rules I would love to see them added
optionally ... 

<BR*/> or <BR*> for that matter ... 


*> Does this sound sensible?

*> CU,
*>     Sec

 ______    __   _
/_  __/_  / /  (_) 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