TextUnit setName() instead of setId() for tuid attribute

[Former user]

Original [issue 188](https://code.google.com/p/okapi/issues/detail?id=188) created by robert.va... on 2011-10-10T09:44:48.000Z:

Hi,

try this code:

TextUnit tu = new TextUnit("myId"); tu.setSourceContent(new TextFragment("Haho"));

TMXWriter writer = new TMXWriter("file\_path..."); writer.writeTUFull(tu);

The expected output would be:

<tu tuid="myId"> <tuv xml:lang="en-gb"> <seg>Haho</seg> </tuv> </tu>

instead I get:

<tu tuid="autoID1"> <tuv xml:lang="en-gb"> <seg>Haho</seg> </tuv> </tu>

The solution is to use setName():

TextUnit tu = new TextUnit(); tu.setSourceContent(new TextFragment("Haho")); tu.setName("myId");

I'm using the Java API of Okapi, v. 0.14

tuid means Translation Unit ID so I'd expect to use the ID (in the constructor for instance) instead of name.

However ID does work if I'm using:

writer.writeTU(new TextFragment("Haho"), new TextFragment("Hoha"), "myId", null);

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=188#c1) originally posted by @ysavourel on 2011-10-21T02:41:55.000Z:

Actually the semantic of TMX tuid is different from the of of Okapi's resource id: a resource id is unique within its type of resource, while the value of TMX tuid is undefined, and there are sometimes duplicates. And since we have to read as well as write we can't match tuid with id.

In that sense it corresponds more to the resource's name, which is based on XLIFF's resname: something that is usually a unique id, but depending on the original format can have duplicates (like in Win resource files (ID\_STATIC)).

One thing we could do when writing out with TMXWriter is use the name first, like now, but if the name is not present, instead of generating some auto-value, we could fallback to the id.

Would this sound a valid work around?

[Former user]

Comment [2.](https://code.google.com/p/okapi/issues/detail?id=188#c2) originally posted by @ysavourel on 2011-10-21T02:42:46.000Z:

[Former user]

Comment [3.](https://code.google.com/p/okapi/issues/detail?id=188#c3) originally posted by @fliden on 2012-06-06T05:25:25.000Z:

The tmx filter maps tmx tuid to okapi name as well so I suggest we keep the reader and writer consistent. I think it will get too confusing if we start mixing it up. The bottom line is that TextUnit id needs to be unique and Tmx tuid does not. Since there's no follow-up response I suggest we close this issue.

[Former user]

Comment [4.](https://code.google.com/p/okapi/issues/detail?id=188#c4) originally posted by @ysavourel on 2012-06-06T11:33:10.000Z:

I tend to agree. Let's see what the other think at the next teleconf.

[Former user]

Comment [5.](https://code.google.com/p/okapi/issues/detail?id=188#c5) originally posted by @fliden on 2012-06-08T20:28:50.000Z: