W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2009

Re: <title> containing markup

From: Chris Lilley <chris@w3.org>
Date: Mon, 23 Mar 2009 16:21:29 +0100
Message-ID: <209757189.20090323162129@w3.org>
To: Cameron McCormack <cam@mcc.id.au>
CC: public-svg-wg@w3.org
On Sunday, March 22, 2009, 10:30:30 AM, Cameron wrote:

CM> One aspect of SVG-in-text/html that we discussed recently was that we
CM> would request that <title> be parsed as RCDATA.  Sam Ruby points out
CM> that SVG 1.1 states that <title> “can contain marked-up text from other
CM> namespaces”[1].  I don’t think I remembered/realised that SVG 1.1 said
CM> that at the time.

It said this to allow extensibility, and also because the I18N Core WG recommends that human-readable text be element content not attributes, specifically so that it can contain markup (eg to indicate the language, where it contains multilingual text).

CM>   SVG Tiny 1.2, on the other hand, says that it must
CM> contain just text. 

We did this because people were asking for specifics of how an SVG implementation would handle every possible case, including a title element containing a complete html document with tables, lists, etc.

The path of least resistance, infortunately, was to remove the capability to have any markup. Yes, that removes the I18N feature as well.

CM>  Does this impact our decision?

CM> I’m wondering also if someone could tell me the exact i18n problems
CM> allowing markup rather than plain text solves.  Do the Unicode bidi
CM> control characters (like RLE, PDF, etc.) not allow you to do everything
CM> you need to?

They let you change direction. They don't let you say what the language is of substrings. I guess the canonical use case is a title containing two characters, one Chinese and one Japanese, which have been unified in Unicode and which are typically rendered with different glyphs depending on the language.

CM>   If there isn’t a compelling reason here to allow markup,
CM> then I’m in favour of keeping our request for it to be parsed as RCDATA
CM> in HTML 5.

CM> [1] http://intertwingly.net/blog/2009/03/20/Accessible#c1237676209





-- 
 Chris Lilley                    mailto:chris@w3.org
 Technical Director, Interaction Domain
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG
Received on Monday, 23 March 2009 15:21:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 March 2009 15:21:43 GMT