Re: Broken i18n and the new UI handler.

Daniel Veillard <Daniel Veillard w3 org> writes:
> > GMarkup basically accepts:
> > 
> >  - elements and attributes <foo bar="baz"></foo>
> >  - the empty-element shortcut <foo bar="baz"/>
> >  - the standard 5 entities &lt; &gt; &apos; &quot; &amp;
> >  - character references &#3424;
> >  - UTF8 encoding
> >  - parses processing instructions and comments, but doesn't do 
> >    anything with them (just passes them through in an opaque node,
> >    and resaves them, but with no interpretation)
> > 
> > It will not handle cdata, custom entities, DTDs or validation, 
> > etc.
>   Correspond more or less to SML an XML simplified version developped
> by some people using XML for purely data centric use:
>  but SML is even smaller than your subset (or was supposed to, I didn't
> heard much about it lately),

Wow, the resemblance is actually uncanny. ;-) The only thing I did
differently was include attributes, they punted attributes. I guess
they also die on processing instructions, while I pass them through.

>   I have no problem with GMarkup, I understand where you come from
> and the reasons. As long as people are not pointed to GMarkup as being
> a generic XML parser, it makes sense.



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