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 3317 - Linking of versions of textual segments via "localization information" data category
Summary: Linking of versions of textual segments via "localization information" data c...
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: WorkingDraft
Hardware: PC Windows XP
: P2 normal
Target Milestone: AfterLC
Assignee: Felix Sasaki
QA Contact: Felix Sasaki
Keywords: changeDeclined, reviewerSatisfied
Depends on:
Reported: 2006-06-07 05:54 UTC by Felix Sasaki
Modified: 2006-10-03 14:41 UTC (History)
1 user (show)

See Also:


Description Felix Sasaki 2006-06-07 05:54:39 UTC
See , from Werner Donne :
[[[4) With the localization information data type it is possible to
    attach information in the form of a message to the translator.
    A use-case I'm considering for my application is to add in the
    document, which is generated for translation, the previous
    version of the concerned paragraph in the master language, as
    well as its translation in the target language. For this it
    would be necessary to link the two paragraph versions to the
    one that is to be translated. A possibility is a "locRef"
    attribute of type NMTOKENS that contains the IDs of the extra
    paragraphs or an alternative locInfoType "reference", in which
    case the locInfo attribute would contain those IDs. The extra
    paragraphs could then be wrapped in a local locInfo element
    or be tagged with the locInfo attribute of locInfoType "auxiliary".
    Those are just suggestions.]]
Comment 1 Felix Sasaki 2006-06-20 05:12:36 UTC
Added Werner to the CC list.
Comment 2 Felix Sasaki 2006-07-24 12:31:54 UTC
Hello Werner,
This is a resonse from the ITS Working Group.

We decided not to make any changes. This is also related to comments we received from the i18n core working group, see comment 12 at .
This issue is also related
to (renaming of
"locInfo" to "locNote"), discussed at .

Does our resolution reply to your concerns? If we don't here from you within 2
weeks, we will regard the issue as closed. Regards, Felix Sasaki.
Wait: answer sent, wait respone.
Comment 3 Werner Donn 2006-08-07 10:16:29 UTC
Hi Felix,

Sorry for the late reply. I was out for two weeks.

I agree with the resolution. My proposal was in fact trying to encode a new type of data in an existing data category. It is indeed much better to be explicit about a new requirement and give it a proper place when it appears to be valuable enough.

Best regards,

Comment 4 Felix Sasaki 2006-09-06 14:16:08 UTC
Closed. Commentor satisified.
Comment 5 Felix Sasaki 2006-09-27 12:37:47 UTC
Summary: The Working Group declined to change the specification. In addition, the name of the data category was changed to "localization note", to clarify its intention. See also issue .