W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2006

Re: Behavior for ITS elements in document instances

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 11 Jul 2006 10:19:54 +0900
Message-ID: <44B2FCBA.4030304@w3.org>
To: Yves Savourel <yves@opentag.com>
Cc: public-i18n-its@w3.org
Hi Yves, all,

Yves Savourel wrote:
> Hi everyone,
> 
> I don't think we have followed up on the start of discussion we had last meeting about the process of ITS elements when they are
> inside a document. (See http://www.w3.org/2006/07/05-i18nits-minutes.html#item06)
> 
> Currently I think the three implementations we have assume these ITS elements are "invisible". That it, we act like they are not
> there: for example, we don't extract as translatable any <locInfo> content.
> 
> I also think there is no mention of any specific behavior for ITS elements in the specification. So, currently the implementations
> (and some examples) are 'wrong'.
> 
> Richard pointed out that, in some cases, we may have to apply localization action to such content.

Note that this requirement does not contradict my proposal below. That
is, you can write "rules about rules" separately, e.g.
<its:translateRule selector="//its:locInfo" translate="yes"/>
of course such rules about rules can be even in a separate file.

Cheers,
Felix

> 
> Felix proposed: "have the rule "data category processing should exclude markup from that data category". This would mean (I think)
> for example that the locInfo data cat would not be applied to <locInfo>, but translatability, directionality, etc. would be.
> 
> Any ideas, suggestions, comments on this topic?
> 
> Cheers,
> -yves
> 
> 



Received on Tuesday, 11 July 2006 01:20:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:07 UTC