Ok now I have another question. If I have keys that are already translated, is it possible to put the translation in the .sdlxliff? Or should I display only the keys that are not translated?

Dan Jakubowicz

You mean you have a mixture of translated keys and non-translated keys?  Examples would be far easier to understand.

Dan Jakubowicz said:

{

  "Name": "Name",

  "Apple": "Apple",

  "Orange": ""

}

Exactly like this example, the value of the key is the translation. 

Dan Jakubowicz

So not a mixture... all of them are translated already?  So what do you mean by "put them in the SDLXLIFF"?  When you open the file with your custom filetype they will be in the SDLXLIFF.  So what EXACTLY do you mean?

- do you want to edit the source and change it so that you have the original source in there?

- do you already have files with a non-translated key and you want to create an SDLXLIFF that has both the translated and non-translated versions?

You're really not helping here. If you just explained properly what you've got now, what you're attempting to do, and what you want at the end of it then I'm sure I can provide you with a better answer.

The example I gave is what my JSON looks like, the key is what to translate and the value is the translation. In SDL studio when I open the file for translating I want the key to be on the left side and the value on the right side. If a key already has already a translation, that means there is something in the value, so when I open the file for translating there should be the key on the left side and the translation on the right side. If the key has no value, that means there is no translation, then the right side should be empty.

Is it enough clear? ^^'

Dan Jakubowicz said:

"Orange": ""

Ah... ok, it just dawned on me.  Do you mean you want to use the value of the key as the translated text?  If this is the case I wouldn't use Trados for this at all.  I'd use a text editor and a bit of regex.  Much faster.

Well, I just wanted to be simple for the translator to have a nice interface. 

Anyway I think I got it to work with "simple delimited text", it automatically put the value for the translation but the problem is : if the line end with a comma, then it thinks that the comma is the translation :/ 

Dan Jakubowicz

Dan Jakubowicz said:

Is it enough clear? ^^'

Yes.

Dan Jakubowicz said:

If a key already has already a translation, that means there is something in the value, so when I open the file for translating there should be the key on the left side and the translation on the right side.

This is not possible on the basis of you having the key on the left and the translated value on the right. The solution I gave you earlier will only allow you to translate the key as a monlingual file.  So the result will be a new file with a translated key but the actual translated content will be exactly the same as it was before translation.  Studio doesn't have a bilngual text filetype... I wish it did.

A possible solution would be to use the Bilingual Excel filetype instead.  If you import into Excel (based on your simple example) and use colon as the delimiter you get this:

Now open in Studio with these settings:

Looks like this in Studio:

Now you have the key on the left and the translated content on the right.  Translate the files, save the target to get a translated Excel file and then reverse the process to get your JSON file back.

Bit of a workaround... maybe someone else has a better idea.

Dan Jakubowicz

Dan Jakubowicz said:

Is it enough clear? ^^'

Yes.

Dan Jakubowicz said:

If a key already has already a translation, that means there is something in the value, so when I open the file for translating there should be the key on the left side and the translation on the right side.

This is not possible on the basis of you having the key on the left and the translated value on the right. The solution I gave you earlier will only allow you to translate the key as a monlingual file.  So the result will be a new file with a translated key but the actual translated content will be exactly the same as it was before translation.  Studio doesn't have a bilngual text filetype... I wish it did.

A possible solution would be to use the Bilingual Excel filetype instead.  If you import into Excel (based on your simple example) and use colon as the delimiter you get this:

Now open in Studio with these settings:

Looks like this in Studio:

Now you have the key on the left and the translated content on the right.  Translate the files, save the target to get a translated Excel file and then reverse the process to get your JSON file back.

Bit of a workaround... maybe someone else has a better idea.