"XHTML 1.0 Transitional, everything validates" - does it ?

Next topic

Author	Message
Sean Kelly	Tuesday 13 September 2005 2:10:39 pm The eZ Publish site states that everything validates against XHTML 1.0 Transitional. When I ran one of my pages (v3.6) through the validator at w3.org it complains that my pages contain un-escaped ampersands. The validator is actually picking up text that I have entered rather than errors in any of the HTML tags. Should eZ Publish be changing ampersand characters in the text that users enter into the proper escaped HTML version? Thanks, Sean.
Gabriel Ambuehl	Wednesday 14 September 2005 3:52:18 am I thought it was perfectly acceptable to use special chars in XHTML 1.0 without escaping them to entities? Would seem like a flaw in the validator to me. Visit http://triligon.org
Nathan Kelly	Wednesday 21 September 2005 9:13:24 pm If you are typing an ampersand into an XML field it should be presented in its encoded form. I think however if you type an ampersand into a textline or textblock you need to wash the output from the template using the \|wash operator: {$node.name\|wash} Will the more knowledgeable please correct me if I'm wrong? <i>Gabriel</i>: Last time I checked non-encoded ampersands only triggered a notice in the validator, not an error or warning! Though I think there is a higher warning level when using a strict doctype. Cheers! Pardon me while I burst into flames...

Author

Message

Tuesday 13 September 2005 2:10:39 pm

The eZ Publish site states that everything validates against XHTML 1.0 Transitional. When I ran one of my pages (v3.6) through the validator at w3.org it complains that my pages contain un-escaped ampersands.

The validator is actually picking up text that I have entered rather than errors in any of the HTML tags.

Should eZ Publish be changing ampersand characters in the text that users enter into the proper escaped HTML version?

Thanks,

Sean.

Gabriel Ambuehl

Wednesday 14 September 2005 3:52:18 am

I thought it was perfectly acceptable to use special chars in XHTML 1.0 without escaping them to entities?

Would seem like a flaw in the validator to me.

Visit http://triligon.org

Nathan Kelly

Wednesday 21 September 2005 9:13:24 pm

If you are typing an ampersand into an XML field it should be presented in its encoded form. I think however if you type an ampersand into a textline or textblock you need to wash the output from the template using the |wash operator:

{$node.name|wash}

Will the more knowledgeable please correct me if I'm wrong?

<i>Gabriel</i>: Last time I checked non-encoded ampersands only triggered a notice in the validator, not an error or warning! Though I think there is a higher warning level when using a strict doctype.

Cheers!

Pardon me while I burst into flames...