W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

[Bug 23208] Attributes and translation

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Jan 2014 14:57:30 +0000
To: www-international@w3.org
Message-ID: <bug-23208-4285-7PfS7228Mg@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23208

Felix Sasaki <fsasaki@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fsasaki@w3.org

--- Comment #3 from Felix Sasaki <fsasaki@w3.org> ---
(In reply to Erika Doyle Navara from comment #2)
> It seems that the most intuitive behavior would be to only translate
> translatable attributes when their element is in the translate-enabled
> state, and in all other cases not to translate an element's attribute
> values. 
> 
> As I read it, this is the behavior currently described in the spec, but I'd
> be happy to take a stab at making this more explicit:
> 
> https://github.com/w3c/html/commit/572aa7b55bcf60eb7f1e8642f1203229ad20e70c
> 
> Is there usage data or use cases suggesting otherwise? I'm having a hard
> time imagining why one might want to translate the translatable attributes
> but not the text node children of an element.
> 
> If the clarification looks okay, I'll merge it into the HTML5 CR spec.

The clarification looks good to me.

- Felix

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You reported the bug.
Received on Tuesday, 7 January 2014 14:57:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:36 UTC