Hi Paul

I know about the discussion around allowing source editing. As you say, the main concern was that translators modify the source without informing the author. This is why Studio requires this function to be explicitly enabled.

In the present scenario where I work on lists of message strings for a simulator, I would assume that if I explicitly allow source editing, changes to the source column should be reflected in the target Excel. I consider this a bit differently from the translation of a Word file for example, where the target file only contains the text in the target language . In this case, the target file contains again the two columns (source and target), it would therefore be logical that both are updated.

At least this is my opinion on this.

I haven't done any test yet with other bilingual formats, being under pressure now because I had to find a workaround to this, but I may do this sometime next week. 

I suggest that this behavior be discussed and if it is the behavior by design, that it be reconsidered.

Walter

Unknown said:

I guess the workaround might be simple enough... export the sdlxliff to Excel with the batch task export to excel, then copy the source column as text only over your target source.

Hi Paul

BTW, which "batch task export to excel" do you mean?

Walter