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

Re: [Comment on ITS WD] Hard to know what this is about

From: Felix Sasaki <fsasaki@w3.org>
Date: Mon, 11 Sep 2006 11:44:23 +0900
Message-ID: <4504CD87.7010900@w3.org>
To: ishida@w3.org
Cc: www-i18n-comments@w3.org, public-i18n-core@w3.org, public-i18n-its@w3.org

Hello i18n core,

This is a reply on behalf of the i18n ITS working group. See also
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3495 for our discussion.

Thank you very much for your comment. We agreed to implement it. Please
have a look at
http://www.w3.org/International/its/itstagset/itstagset.html#elements-within-text
.


Please let us know within 2 weeks if you are satisfied. If we don't hear
 from you , we will assume this issue as closed.

Regards,

Felix


ishida@w3.org wrote:
> Comment from the i18n review of:
> http://www.w3.org/TR/2006/WD-its-20060518/
> 
> Comment 23
> At http://www.w3.org/International/reviews/0606-its/
> Editorial/substantive: E
> Owner: RI
> 
> Location in reviewed document:
> 6.8.1
> 
> Comment: 
> The definition of flow of content as 'representing how the nodes of the element should be treated as a single unit for linguistic purposes' is not only hard to read, but doesn't tell me anything about its intended use. Could we be talking about identifying noun phrases?
> 
> 
> I think we are talking about identifying translation unit segmentation breaks. If this is the case, please make that clear. I think people reading this could be either unclear about its intent, or misunderstand in such a way that it is implemented for all sorts of uninteroperable structural definitions of the content.
> 
> 
> 
> 
Received on Monday, 11 September 2006 02:44:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:51 GMT