- From: <bugzilla@jessica.w3.org>
- Date: Mon, 01 Apr 2013 19:27:11 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21495
Bug ID: 21495
Summary: List of translatable elements and attributes
Classification: Unclassified
Product: HTML WG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: CR HTML5 spec
Assignee: robin@w3.org
Reporter: ysavourel@enlaso.com
QA Contact: public-html-bugzilla@w3.org
Looking at the editor's draft here:
http://www.w3.org/html/wg/drafts/html/master/dom.html#the-translate-attribute
a) Base on the current definition, there is no way to know for sure when the
content attribute on meta elements is transltable or not.
"...if the name attribute specifies a metadata name whose value is known to be
translatable" does not really help. I would suggested to provide a list of
names corresponding to a translatable content attribute, and possibly add that
other values may exist. This would provide at least a set of testable values
and some level of predictable behavior.
b) I don't think the lang attribute can be considered translatable. Its value
should be updated in some cases, but it's not a translatable value. For
example, on can have an application that takes an HTML input and creates an
output that is not the translated HTML document (e.g. to create bilingual data
to train MT engines, etc.), the value of lang doesn't belong to such data set.
c) The style element is defined as translatable, but its content is not HTML
markup and I would not consider it part of the translatable element. Parts of
its content may need translation, just like parts of a JavaScript content may
need translation, but in both cases the content to process is not HTML.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 1 April 2013 19:27:14 UTC