[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] a quick question regarding the Localization Note mapping in XLIFF 2.1
The Localization Note maps to two Core features:
a) The <note> element, with locNoteType set through priority=’1’ as an ‘alert’ and other values as a ‘description’
b) The comment annotation with either value or ref, but it misses a locNoteType, so we have to provide it through itsm.
BTW: as I said a few times already, I really think having all the ITS mapping defined in a single section, per data category would be a lot easier to understand than having that split into several parts.
Also, I’m not sure why some parts would not be normative: For example, defining the translate attribute as the mapping to the Translate data category is normative in my opinion.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Dr. David Filip
Sent: Thursday, November 20, 2014 5:30 AM
To: email@example.com; firstname.lastname@example.org
Subject: [xliff] a quick question regarding the Localization Note mapping in XLIFF 2.1
in the current working draft of XLIFF 2.1 I list the Localization Note category under the partially supported categories.
Now, on partially supported categories we have an informative description how XLIFF features can be used and then we add in the normative ITS module what's needed to fully support that category.
Now I was going to add what's needed to fully support the Localization Note, but cannot think of anything that is not expressed by the core mechanism.
Should I move the category to fully supported?
Or someone please tell me what other elements, attributes, or even values we need to define in XLIFF in order to fully support that category.