W3C home > Mailing lists > Public > www-i18n-comments@w3.org > September 2006

RE: [Comment on ITS WD] Translatability

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 22 Sep 2006 20:48:41 +0900 (JST)
Message-ID: <2560.219.160.130.186.1158925721.squirrel@webmail.w3.mag.keio.ac.jp>
To: "Richard Ishida" <ishida@w3.org>
Cc: www-i18n-comments@w3.org, public-i18n-core@w3.org, public-i18n-its@w3.org

>
> Thanks for making these changes Yves.  This is editorial, so just to you.

Hi Richard,

I agree with your change proposal regarding the markup and think also this
is only editorial.
I don't think we should give up the capitalization of the first letter:
I'm sure people will write about ITS in printed text, and in some cases
they might not have specific styling available. This would look a kind of
weird, e.g. like:

"The data category translate expresses information about ..."

So I'd still prefer

"The data category Translate expresses information about ..."

Cheers,

Felix

>
> I think you should put the link text around just the name of the data
> category, ie. <a>translate</a> data category, not <a>Translate data
> category</a>.  This is
>
> 1. more consistent with common practice
> 2. more consistent with other parts of the ITS doc, eg. you don't
> currently
> highlight more than 'selector' in "A required <>selector<> attribute ..."
> 2. more closely semantic markup - ie. the thing we are marking with the
> text
> is the data category name 'translate' or 'terminology', no need to
> highlight
> 'data category'.
>
> Also, given that we have distinctive styling and markup, I don't think we
> need to capitalise the initial letter.
>
> The links as they stand (particularly with the capitalisation) look more
> like typical links to section headings than markup of keywords (which is
> what is needed).
>
> Hope that helps,
> RI
>
>
> ============
> Richard Ishida
> Internationalization Lead
> W3C (World Wide Web Consortium)
>
> http://www.w3.org/People/Ishida/
> http://www.w3.org/International/
> http://people.w3.org/rishida/blog/
> http://www.flickr.com/photos/ishida/
>
>
>> -----Original Message-----
>> From: Yves Savourel [mailto:ysavourel@translate.com]
>> Sent: 20 September 2006 21:38
>> To: 'Richard Ishida'
>> Cc: www-i18n-comments@w3.org; public-i18n-core@w3.org;
>> public-i18n-its@w3.org
>> Subject: RE: [Comment on ITS WD] Translatability
>>
>> Hi Richard,
>>
>> The name of the data category "Translatability" has been
>> changed to "Translate", and the text has been modified
>> accordingly. See:
>> http://www.w3.org/International/its/itstagset/itstagset.html
>>
>> 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.
>>
>> Thanks
>> -yves
>>
>> -----Original Message-----
>> From: public-i18n-its-request@w3.org
>> [mailto:public-i18n-its-request@w3.org] On Behalf Of Richard Ishida
>> Sent: Wednesday, September 13, 2006 5:45 AM
>> To: public-i18n-its@w3.org
>> Cc: www-i18n-comments@w3.org; public-i18n-core@w3.org
>> Subject: RE: [Comment on ITS WD] Translatability
>>
>>
>> The i18n Core WG still feels that 'translatability' is
>> incorrect for describing this data category, since it is
>> typically used to describe whether something has been enabled
>> for translation, rather than whether something should be
>> translated or not.
>>
>> We would like the ITS group to consider one more time whether
>> this can be changed.
>>
>> Suggested alternatives:
>> Translate
>> Translate flag
>> Translate switch
>> Translate information
>> Translate directive
>>
>>
>> Thanks,
>> RI
>>
>> ============
>> Richard Ishida
>> Internationalization Lead
>> W3C (World Wide Web Consortium)
>>
>
>
>
Received on Friday, 22 September 2006 11:48:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:32:36 GMT