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

Re: Translation control in HTML5

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 02 Dec 2008 23:08:23 +0900
Message-ID: <49354157.5020708@w3.org>
To: Ian Hickson <ian@hixie.ch>
CC: public-html@w3.org, www-international@w3.org

Hello Ian,

Ian Hickson さんは書きました:
> (Trimmed cc's to avoid excessive cross-posting; re-added www-international 
> on request.)
>
> I read through all the feedback on this topic.
>
> There doesn't seem to be a really common enough use case for adding a 
> feature to the core language to handle it. However, I do agree that this 
> is something that is an issue for some authors and implementors. I would 
> recommend approaching the Microformats community and minting a class 
> value, possibly reusing class="notranslate" [1], to handle this.
>
> I would also recommend not translating the contents of <code>.
>
> As has been noted, for more in-depth control, the ITS vocabulary is 
> probably the better solution; indeed an ITS tranlation rule set [2] could 
> be used to define the processing of a microformat formally. 

Just a clarification question: Do you think that rule set should only be 
used to define the processing of the microformat, e.g.
<its:translateRule selector="//*[@class='notranslate']" translate="no"/>
or also for describing defaults like what you proposed e.g. for code, e.g.
<its:translateRule selector="//code" translate="no"/>

Felix

> It may make 
> sense to come up with a way to have external ITS files defining rules and 
> link to them from HTML files using a <link rel=""> keyword; if this is 
> desired, I would recommend writing up the semantics of such a keyword in a 
> separate document, and then listing the keyword on the WHATWG 
> RelExtensions wiki, so that it gets registered when we finalise the 
> solution for rel value registration.
>
> [1] http://googlewebmastercentral.blogspot.com/2008/10/helping-you-break-language-barrier.html
> [2] http://www.w3.org/TR/2007/REC-its-20070403/#rules
>
>   
Received on Tuesday, 2 December 2008 14:09:05 GMT

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