This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3481 - Translatability
Summary: Translatability
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: LastCall
Hardware: PC Windows XP
: P2 normal
Target Milestone: AfterLC
Assignee: Felix Sasaki
QA Contact: Felix Sasaki
Keywords: proposalAccepted, reviewerSatisfied
Depends on:
Reported: 2006-07-18 18:48 UTC by Yves Savourel
Modified: 2006-10-03 14:48 UTC (History)
0 users

See Also:


Description Yves Savourel 2006-07-18 18:48:53 UTC
Issue #5 of i18nCore comments:

Section 6.2: 'Translatability' is not a good term for this, since it is already used in the sense of internationalization to allow for easy translation. Perhaps "Translation information" would be better, and more consistent with other data category titles.

FS: The first ITS WD already talks about "translatabilty". So does the requirements document . Given this long history of the term which you must be aware of, I disagree with your request to change it. I also disagree with your argument of consistency with other data categories: Our envisaged users are likely to focus only on a subset of data categories, see also the conformance section which separates data categories. Hence, consistency of naming is not so important, but rather consistency between ITS working drafts, implementations, presentations, ... . 

I18n: There is no need to be consistent in this regard with past working drafts. People should expect Working Drafts to change, as described in the status section. There is a much greater need to go forward with appropriate terminology.

We don't see that this is a difficult change to make. 

"Our envisaged users are likely to focus only on a subset of data categories" We believe this is irrelevant to appropriate naming of a given data category, but in addition I don't think you are proposing that the 'translatability' category will always be used independently of other implementations, so I don't think this argument holds. 

We may be prepared to accept that 'Translation Information' is too vague. Alternative suggestions for the title are 'Translate Information' or 'Translate Directive'.
Comment 1 Felix Sasaki 2006-07-25 05:23:26 UTC
Action: working group to discuss and reply.
Comment 2 Felix Sasaki 2006-07-25 05:25:20 UTC
Discussed at . Action: working group to continue discussion.
Comment 3 Felix Sasaki 2006-08-01 01:15:04 UTC
Discussed at . Resolution: we propose not to change the name of the data category, and keep "translatability".
Comment 4 Felix Sasaki 2006-09-07 04:02:44 UTC
Action: Felix to go back to i18n core
Comment 5 Felix Sasaki 2006-09-11 00:53:20 UTC
Wait: response sent. See
Comment 6 Yves Savourel 2006-09-21 13:43:56 UTC
After further discussion, WG agreed to change "Translatability" to "Translate".

The change has been made, and the ID and IDREFs have been changed from translatability to trans-datacat.
Comment 7 Felix Sasaki 2006-09-21 14:05:57 UTC
Wait: response sent. See .
Comment 8 Felix Sasaki 2006-09-26 10:41:18 UTC
Closed. Reviewer satisfied. See .
Comment 9 Felix Sasaki 2006-09-28 06:31:19 UTC
Summary: The Working Group decided to accept the proposal and to change the name of the data category "translation information" to "Translate".