Re: env.xml validation problem

2002-08-23 Thread Erik Abele
Justin Erenkrantz wrote: On Fri, Aug 23, 2002 at 07:41:59PM -0400, Joshua Slive wrote: I certainly don't recommend changing the actual env variable. I wouldn't have chosen that name myself, but it's done now and I'm fine with it. Which is precisely my point. -- justin and everyone is happy :-)

Re: env.xml validation problem

2002-08-23 Thread Justin Erenkrantz
On Fri, Aug 23, 2002 at 07:41:59PM -0400, Joshua Slive wrote: > Sorry Justin. It seems I'm always picking on you lately ;-) Heh. No offense intended or taken. If we agreed on everything, this world would be a boring place... (In all honesty, I was going to bring up the issue of renaming it bef

Re: env.xml validation problem

2002-08-23 Thread Joshua Slive
Justin Erenkrantz wrote: It was a crummy name for the env variable, and it was a crummy name for the id. Why? gzip-only-text/html is what it does. -0 on changing the / in the env just because our docs don't like it. -- justin Sorry Justin. It seems I'm always picking on you lately ;-) I certai

Re: env.xml validation problem

2002-08-23 Thread David Shane Holden
Astrid Keßler wrote: > > An id has to be unique within the doument. CDATA not. Since the id > attribute will become an anchor in the generated html file, uniqueness > is postulated. > > An id comes with some restrictions. The same restrictions (and more, if > I'm not mistaken) applys to anchors. Wh

Re: env.xml validation problem

2002-08-23 Thread Erik Abele
Astrid Keßler wrote: Gotta change the DTD -1 Also -1 from me. I asked because I knew that we will have to keep the ID state in the dtd :-) or the id +1 Seems to be the only way. I just hope that nobody is relying on the consistency of directive-/env-names and IDs/anchors. I will commit this. A

Re: env.xml validation problem

2002-08-23 Thread Justin Erenkrantz
On Fri, Aug 23, 2002 at 07:14:22PM -0400, Joshua Slive wrote: > André Malo wrote: > > > >I suggest to rename the mentioned ID to "gzip-only-text-html". > > +1 > > It was a crummy name for the env variable, and it was a crummy name for > the id. Why? gzip-only-text/html is what it does. -0 on

Re: env.xml validation problem

2002-08-23 Thread Joshua Slive
André Malo wrote: I suggest to rename the mentioned ID to "gzip-only-text-html". +1 It was a crummy name for the env variable, and it was a crummy name for the id. Joshua. - To unsubscribe, e-mail: [EMAIL PROTECTED] For addition

Re: env.xml validation problem

2002-08-23 Thread André Malo
* Astrid Keßler wrote: >> Gotta change the DTD > > -1 > >> or the id > > +1 > >> . Patch attached. > > -1 _ = -1 ;-) > An id has to be unique within the doument. CDATA not. Since the id > attribute will become an anchor in the generated html file, uniqueness > is postulated. > > An i

Re: env.xml validation problem

2002-08-23 Thread Astrid Keßler
> Gotta change the DTD -1 > or the id +1 > . Patch attached. -1 An id has to be unique within the doument. CDATA not. Since the id attribute will become an anchor in the generated html file, uniqueness is postulated. An id comes with some restrictions. The same restrictions (and more, if I'

Re: env.xml validation problem

2002-08-23 Thread David Shane Holden
Erik Abele wrote: > Hi! > > While validating the xml-docs I discovered a problem in env.xml: it seems > that a slash isn't allowed in ID-attributes. > > The parser reports the following error: env.xml:275:39: Attribute value > "gzip-only-text/html" of type ID must be a name. > > from env.xml: > >

env.xml validation problem

2002-08-23 Thread Erik Abele
Hi! While validating the xml-docs I discovered a problem in env.xml: it seems that a slash isn't allowed in ID-attributes. The parser reports the following error: env.xml:275:39: Attribute value "gzip-only-text/html" of type ID must be a name. from env.xml: Removing the slash solves the valida