<[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Quoting Robert Leland <[EMAIL PROTECTED]>: > > > [EMAIL PROTECTED] wrote: > > > > > > > >One issue with this is to make sure the validator DTD is up to date. > > > > > >The reason I say this is because the DTD appears to be missing the > > var-jstype > > >sub-element of the var element. Even the 1.2.0 version of the DTD on CVS is > > > > >missing this. > > > > > >I assume it is a valid element, because even though I can't validate my > > >document, the element is used properly when I set it. > > > > > > > > I just comitted a patch. The DTD is a bit more general than I would > > like, however trhe next 4 days are a crunch for me, but it should work. > > Let me know if there is more problems or you know for sure how to limit > > the variables it takes, see the comment > > in the DTD. > > > > Rob - > > this is a little bit broken, you need to have > <!ELEMENT var (var-name, var-value, var-jstype*)> > instead of > <!ELEMENT var (var-name, var-value, var-jstype)>
If you just want optional, you don't want *, you want ?, like so: <!ELEMENT var (var-name, var-value, var-jstype?)> -- Martin Cooper > > otherwise the var-jstype element is considered required. > > I'm also not an XML guru, but I'm pretty sure that limiting the contents of > the var-jstype element is not possible with DTDs. > > Matt Bathje --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
