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 3460 - Loc Info or Loc Note
Summary: Loc Info or Loc Note
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-14 19:46 UTC by Yves Savourel
Modified: 2016-02-09 10:54 UTC (History)
1 user (show)

See Also:


Description Yves Savourel 2006-07-14 19:46:47 UTC
Comment 12 of i18nCore comments:

Section 6.3.2: Is there any reason that locInfo is not called locNote - since that is much more true to the meaning.

FS: The naming relies on the name of the data category. I don't think that your proposal "locNote" is appropriate, since providing notes is *one* usage of this data category. See a different usage described at (issue 4, "With the localization information data type"), which (possibly automatically) uses "localization information" for adding linking information between different translation versions. Such links are certainly no "notes" and have a different status than e.g. locn-note in the XMLSPEC i18n DTD, see example 20 at . 

I18n: We think there is a serious risk of diluting the meaning of locInfo here to the point that a translation tool, for example, doesn't know what to do with the information pointed to. Pointing to previous translations should be another data category in ITS v2, since the translation tool may well need to do different things with this type of information. That's exactly why I wanted to change the name of the data category - because localization information is too broad a category to describe exactly what this is about. We need to be more specific. Note that the requirements document [1] refers to this specifically as Localization Notes. (If you are going to argue for consistency with that document in comment 6, you should take it into account here, too. ;-)

So the key issue here is what exactly is the scope of the locInfo data category. We feel it should be kept specifically to providing notes to translators, and other similar mechanisms such as pointing to former translations, should be considered more carefully in version 2, when they may well be best implemented as a different data category altogether.


We are raising the status of this comment to S.
Comment 1 Felix Sasaki 2006-07-24 17:04:15 UTC
Resolution: working group agreed with the change at .
Action: editors to implement the change.
Comment 2 Christian Lieske 2006-08-16 12:03:14 UTC

Add the following note in the "definition" section for "localization information":

locInfo is meant to provide notes to translators. Mechanisms such as pointing to former translations, might be considered more carefully in version 2 of ITS.
Comment 3 Felix Sasaki 2006-09-06 15:50:11 UTC
Discussed at .
Summary : we change the name of the data category to localization note, and change the markup to locNote
Yves: no further explanation necessary
Action: editors to make the change
Comment 4 Felix Sasaki 2006-09-11 02:06:27 UTC
Wait: response sent. See
Comment 5 Yves Savourel 2006-09-14 03:41:36 UTC
Closed. Commenters satisfied see:
Comment 6 Felix Sasaki 2006-09-28 06:15:58 UTC
Summary: The Working Group has accepted the proposal and changed the name of the data category from "localization information" to "localization note", and the element and attribute names respectively.