W3C home > Mailing lists > Public > public-html@w3.org > July 2008

Re: Translation control in HTML5

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 31 Jul 2008 22:33:28 +0000 (UTC)
To: Jirka Kosek <jirka@kosek.cz>
Cc: David Muschiol <david@david-muschiol.de>, public-html@w3.org
Message-ID: <Pine.LNX.4.62.0807312228280.3295@hixie.dreamhostps.com>

On Fri, 1 Aug 2008, Jirka Kosek wrote:
> Ian Hickson wrote:
> > On Thu, 31 Jul 2008, Jirka Kosek wrote:
> > > > Very good point.  lang="only de" would also work here while even being
> > > This would completely break syntax of lang attribute values which should
> > > be following BCP 47 (http://www.rfc-editor.org/rfc/rfc4646.txt)
> > 
> > We define lang, we can easily define it as being something akin to:
> > 
> >    [only] <bcp-47-code>
> 
> And what is point in doing it differently from dozens of other markup 
> languages?

The main benefit of this proposal is that it would automatically work in 
already shipped tools. It also avoids adding yet another global attribute, 
especially one for a relatively minor use case, with an unproven track 
record (i.e. we don't know if authors will use it anyway).


> Moreover, having separate lang and translate attributes will be much 
> more friendly to CSS selectors.

That's certainly an important advantage of keeping these in separate 
attributes, yes. We have to balance all the various pros and cons in 
coming up with a solution (assuming we want to address this use case).

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 31 July 2008 22:34:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:19 GMT