Hi Samuel & Luke,

I'm a bit confused by this:

Samuel Murray said:

when I opt not to select the target language (as it is "optional", after all)

Why wouldn't you select a target language?  If you don't, and if the application allowed it, how would it know what other language resources to use?  This feels a little odd discussing an error for something that seems to have no point at all.  Or am I missing something obvious here?

Regards

Paul

Hello Samuel,

Samuel Murray said:

I was trying out various ways of creating SDLXLIFF files, because I wanted to find out how SDLXLIFF files without a set target language are possibly created

When you create a Project using the Project wizard several things happen:

1. a copy of the files you select are taken and placed into the source language folder created for the Project
2. these source files are converted to an sdlxliff with no target language and also placed in the source language folder
3. copies of these sdlxliff files, with target languages are created and copied into separate folders for whichever target languages you are working into

If, during the Project you decide to add an additional language for translation, then these source language only files are used as the basis of the new sdlxliff files created for the new languages.

Samuel Murray said:

The fact that the dialog allows me to not select the target language (and also specifically says that it is optional) makes me believe me that it must be a program feature, and not a bug, and so it must be possible to complete the file creation process with that setting.

It is possible to complete the process if you do work with one of these sdlxliff files, but you set the target language and it would not be optional anymore.  The reason it's optional is because you usually bring in monolingual files that don't have a target language yet and you choose one (so the default selection is optional... you can change it), or bilingual files where the target language is already selected and then it's not optional.

What we do see sometimes, and it's not particularly good practice in my opinion, is that some Project Managers will send the source language sdlxliff around to save them effort.  The same file can be sent to translators in all languages.  It was never intended to be used this way, but it does happen.  It can also lead to problems for a Project Manager when the file is returned if the sdlxliff file was not handled in a compatible version of Studio, or another tool altogether for example. Using the correct target language sdlxliff avoids this issue.

I think you've found an interesting issue, but I don't think it's one that is very common as I can't see why anyone would open the sdlxliff for translation without setting the target language first.  So we should address this to either not allow this to happen if you try to move on without setting the language, or use the one that is displayed as optional.

Regards

Paul

Hello Samuel,

Samuel Murray said:

I was trying out various ways of creating SDLXLIFF files, because I wanted to find out how SDLXLIFF files without a set target language are possibly created

When you create a Project using the Project wizard several things happen:

1. a copy of the files you select are taken and placed into the source language folder created for the Project
2. these source files are converted to an sdlxliff with no target language and also placed in the source language folder
3. copies of these sdlxliff files, with target languages are created and copied into separate folders for whichever target languages you are working into

If, during the Project you decide to add an additional language for translation, then these source language only files are used as the basis of the new sdlxliff files created for the new languages.

Samuel Murray said:

The fact that the dialog allows me to not select the target language (and also specifically says that it is optional) makes me believe me that it must be a program feature, and not a bug, and so it must be possible to complete the file creation process with that setting.

It is possible to complete the process if you do work with one of these sdlxliff files, but you set the target language and it would not be optional anymore.  The reason it's optional is because you usually bring in monolingual files that don't have a target language yet and you choose one (so the default selection is optional... you can change it), or bilingual files where the target language is already selected and then it's not optional.

What we do see sometimes, and it's not particularly good practice in my opinion, is that some Project Managers will send the source language sdlxliff around to save them effort.  The same file can be sent to translators in all languages.  It was never intended to be used this way, but it does happen.  It can also lead to problems for a Project Manager when the file is returned if the sdlxliff file was not handled in a compatible version of Studio, or another tool altogether for example. Using the correct target language sdlxliff avoids this issue.

I think you've found an interesting issue, but I don't think it's one that is very common as I can't see why anyone would open the sdlxliff for translation without setting the target language first.  So we should address this to either not allow this to happen if you try to move on without setting the language, or use the one that is displayed as optional.

Regards

Paul

Samuel Murray said:

Or, perhaps they think that that is what one is supposed to do. It makes sense, after all: translators translate from source to target, so you have to send them the "source" file, and then what you get back from them is the "target".

I can see what you mean Samuel.  I guess if they use packages it's never a problem.  It's only when you have Agencies, or small teams sharing work via the sdlxliff itself where these problems can occur.  And if you want to share the sdlxliff around you would have to know which folders to put them back into... clearly the target folder... or their project would not update  So I really doubt this is a mistake.