OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only
  • 1.  original ID for unit

    Posted 11-05-2012 04:06
    Hi all, While going through the review of the latest XLIFF draft to map the ITS metadata, it was found that the equivalent of the 1.2 resname attribute does not exists in 2.0. This information has been used quite a lot in 1.2, for example for ID-based matching, comparison, context information etc. This is especially useful when working with software resources. It would make sense in my opinion to have it also in 2.0. I propose to have an optional 'name' attribute of type string in the <unit> element: Attribute name: name Definition: The original identifier of the resource corresponding to the extracted <unit>. For example: the key in the key/value pair in a Java properties file, the ID of a string in a Windows string table, the index value of an entry in a database table, etc. Example: <unit id='23' name='ID_CANCEL'> <segment> <source>Cancel</source> </segment> </unit> Note that IMO this is not a new feature, just a correction of something missing in unit. Regards, -yves


  • 2.  RE: [xliff] original ID for unit

    Posted 11-05-2012 14:02
    I second. ________________________________________ From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] on behalf of Yves Savourel [ysavourel@enlaso.com] Sent: Sunday, November 04, 2012 8:06 PM To: xliff@lists.oasis-open.org Subject: [xliff] original ID for unit Hi all, While going through the review of the latest XLIFF draft to map the ITS metadata, it was found that the equivalent of the 1.2 resname attribute does not exists in 2.0. This information has been used quite a lot in 1.2, for example for ID-based matching, comparison, context information etc. This is especially useful when working with software resources. It would make sense in my opinion to have it also in 2.0. I propose to have an optional 'name' attribute of type string in the <unit> element: Attribute name: name Definition: The original identifier of the resource corresponding to the extracted <unit>. For example: the key in the key/value pair in a Java properties file, the ID of a string in a Windows string table, the index value of an entry in a database table, etc. Example: <unit id='23' name='ID_CANCEL'> <segment> <source>Cancel</source> </segment> </unit> Note that IMO this is not a new feature, just a correction of something missing in unit. Regards, -yves --------------------------------------------------------------------- To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xliff-help@lists.oasis-open.org