W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [DOM4] XML lang

From: Robin Berjon <robin@berjon.com>
Date: Mon, 14 Nov 2011 18:04:00 +0100
Cc: "Marcos Caceres" <w3c@marcosc.com>, "Jonas Sicking" <jonas@sicking.cc>, public-webapps <public-webapps@w3.org>
Message-Id: <F6980B49-D169-4E3D-A1F2-C8BAEDF4AE6E@berjon.com>
To: Anne van Kesteren <annevk@opera.com>
On Nov 14, 2011, at 16:43 , Anne van Kesteren wrote:
> On Wed, 05 Oct 2011 23:07:44 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
>> As has been pointed out, you can use
>> Element.matchesSelector(":lang('en-us')") or XPath to test if a node
>> has a given language. However neither lets you actually *get* the
>> language of a node, just check if it matches a particular language.
>> Additionally, matchesSelector doesn't work on text nodes.
> 
> We already have baseURI. I suppose we could have another such thing. "lang" is taken unfortunately. "language"? "naturalLang"? (Based on <img>.naturalHeight/Width.)

Not to bikeshed, but how about baseLang? The link with baseURI, even if usurped, at least has a chance of sticking in memory.

> I do not think its exact behavior should be defined in DOM4, but we can certainly introduce the concept and say that other specifications define it. E.g. HTML and XML.

+1

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 14 November 2011 17:04:31 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT