page_title escaping character entities

johnstephens · 2008-12-19 03:35:16

I entered this:

<txp:page_title separator=" &183; " />

And I get this:

My Site &amp;#183; Section

I checked the Textbook, which includes this example:

<title><txp:page_title separator=" &raquo; " /></title>

But if I use » I get &raquo;.

Is there a way to use properly formatted entities as a separator, without turning the & into &?

MattD · 2008-12-19 08:40:23

See ruud’s solution in a similar thread

johnstephens · 2008-12-19 16:19:05

Thanks. I tried that with &183; (AKA ·), which is Shift-Alt-9 on my Mac keyboard: ·

Textpattern didn’t escape it all— the middot appears in the source code exactly as entered in the tag.

And— it successfully validated as XHTML 1.0 Strict. I thought special characters had to be converted into &entities; in order to validate. What’s the truth?

colak · 2008-12-19 16:25:29

johnstephens wrote:

And— it successfully validated as XHTML 1.0 Strict. I thought special characters had to be converted into &entities; in order to validate. What’s the truth?

Special characters should be converted into their entities but not because of validation but rather for cross-platform/browser/system uniformity.

I found that the W3 validator only throws errors with the unescaped ampersands & but copy paste characters shuch as bull emdash etc are not recognised as being problematic.

This, in my view, is a bug with the validator.

johnstephens · 2008-12-19 17:27:17

Thank you, Yiannis.

So, if I want to use this character I shouldn’t use the <txp:page_title /> tag?

ruud · 2008-12-20 07:05:20

In TXP tag attribute values you should not use HTML entities. TXP tags should escape attribute values if needed automatically. In older TXP versions there were a few cases where escaping wasn’t done correctly.

Outside TXP, in the normal HTML code, when using UTF8, the only characters that need escaping are " & > <, because those characters have special meaning in (X)HTML. Using entities for other characters (like ·) is needed only when using a character set that doesn’t support that character, so I think the W3 validator behaviour is correct.

johnstephens · 2008-12-20 18:44:50

Thank you, Ruud, for clarifying that. Is there a good reference somewhere showing what characters are included in utf-8?

colak · 2008-12-20 18:56:49

johnstephens wrote:

Thank you, Ruud, for clarifying that. Is there a good reference somewhere showing what characters are included in utf-8?

Here it is.

Last edited by colak (2008-12-20 18:58:38)

Gocom · 2008-12-20 19:09:08

johnstephens wrote:

Thank you, Ruud, for clarifying that. Is there a good reference somewhere showing what characters are included in utf-8?

Any character in the Unicode standard. Says something? ;) That list of colaks is r-e-a-l-l-y long.

Last edited by Gocom (2008-12-20 19:10:47)

colak · 2008-12-20 19:09:21

And here’s a list apart article on the subject.

Last edited by colak (2008-12-20 19:10:51)

ruud · 2008-12-20 19:14:43

As far as I know, all characters are included in utf8.

Bloke · 2008-12-20 19:18:39

Even Klingon (sort of)

Textpattern CMS

Textpattern CMS support forum

#1 2008-12-19 03:35:16

page_title escaping character entities

#2 2008-12-19 08:40:23

Re: page_title escaping character entities

#3 2008-12-19 16:19:05

Re: page_title escaping character entities

#4 2008-12-19 16:25:29

Re: page_title escaping character entities

#5 2008-12-19 17:27:17

Re: page_title escaping character entities

#6 2008-12-20 07:05:20

Re: page_title escaping character entities

#7 2008-12-20 18:44:50

Re: page_title escaping character entities

#8 2008-12-20 18:56:49

Re: page_title escaping character entities

#9 2008-12-20 19:09:08

Re: page_title escaping character entities

#10 2008-12-20 19:09:21

Re: page_title escaping character entities

#11 2008-12-20 19:14:43

Re: page_title escaping character entities

#12 2008-12-20 19:18:39

Re: page_title escaping character entities

Board footer