W3C home > Mailing lists > Public > www-international@w3.org > October to December 2013

Re: New FAQ Article for review [I18N-ACTION-260]

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 08 Oct 2013 16:10:08 +0200
Message-ID: <52541240.6040907@w3.org>
To: www-international@w3.org
Apologies for the late review. This is a very useful document and will 
help to increase the usage of the "translate" attribute significantly. A 
few suggestions.

1)
" Localization groups may also use external files to point to markup 
that should not be translated (among other things). A way of doing this 
is described by the Internationalization Tag Set (ITS) 
<http://www.w3.org/TR/its20/> specification. Localizers may set up these 
rules in consultation with the content developers."

The mechanism described here is not only for localizers consulting 
content developers; sometimes content developers would specify the 
rules, for usage by various localizers. It could then be a "selling 
point" for the content developer: "my web site (template) is easier / 
faster to localize".
Also, the difference to the translate attribute is that you can set up 
these rules once for several documents. So I'd propose to re-write this 
like the below:

"You may also want to point to several pieces of markup in one document 
or even for a group of documents that should not be translated (among 
other things). For example you may want to express that all "code" 
elements on your Web site should not be translated. A way of expressing 
such rules is described by the <a 
href="http://www.w3.org/TR/its20/#EX-translate-selector-1">Internationalization 
Tag Set (ITS) specification</a>. Content developers and localizers may 
work closely together in setting up these rules to achieve a faster and 
better localization process."



2)
"standards such as XLIFF": add a link to 
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff


3)
I am wondering whether one should mention somewhere: the translate 
attribute will also be recognized by tools (both the online MT tools 
mentioned as well as tools described in the "Metadata for the 
Multilingual Web - Usage Scenarios and Implementations" document) if an 
older HTML version is used.

Sure, HTML 4.01 or XHTML won't validate (so we don't want to recommend 
this) - but this won't break the tools digesting the "translate" 
attribute. The point is that people who may not be able to switch e.g. a 
whole site to HTML5 still have can use the translate attribute.

- Felix

Am 27.09.13 17:06, schrieb Phillips, Addison:
> All,
>
> The Internationalization Working Group has prepared a new version of the FAQ article "Using the HTML5 'translate' attribute". We welcome comments from the community before formally publishing the article.
>
> The article is located here: http://www.w3.org/International/questions/qa-translate-flag
>
> Please send your comments to www-international@ on or before 4 October 2013.
>
> Addison
>
> Addison Phillips
> Globalization Architect (Amazon Lab126)
> Chair (W3C I18N WG)
>
> Internationalization is not a feature.
> It is an architecture.
>
Received on Tuesday, 8 October 2013 14:10:39 UTC

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