<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0"> <TITLE>XLIFF representation</TITLE> </HEAD> <BODY>  Hi, I was looking at the XLIFF PO Guide Draft 2 (<A HREF="http://xliff-tools.freedesktop.org/wiki/Projects_2fXliffPoGuideDraft2">http://xliff-tools.freedesktop.org/wiki/Projects_2fXliffPoGuideDraft2</A>) which is, I think, the latest draft I can access, and I had a question: I noticed that <trans-unit> have an id but no resname. It seems that it would be reasonnable for a software file format to have unique ID, and 'msgid' seems to be capable of doing this. I realize that msgid is really used for the source text, and that leads to make it in pratice not really usable for resname. Many localization tools rely on ID to do things like leveraging, updates, or alignment. It would be nice to have a solution for resname. (One cannot use id as it's just a sequential number). I guess my question goes a little further and touched on the usage of msgid itself. Wouldn't be more efficent from a localization viewpoint to recommend using unique IDs there instead of the source string? That would also follow the concept of treating the source language as "just another language". Just a thought. Kind regards, -yves </BODY> </HTML>