Unknown said:

The idea behind merging is working in a single file (to make life easier I guess). What is the point of being able to merge files, edit them, and then having no way to update the original single files?

Hi Spiros Doikas of course I agree and you could achieve this by using the merge in the project after you created it rather than merge them before.  In fact you remove all possibilities of handling them any other way at all if you merge them beforehand.  However, I think this is something we already know about but it doesn't have a high priority to resolve, mainly because the process works perfectly for non-sdlxliff files and you have a workaround by using what many would consider a better solution anyway by merging them after the project is created and then you won't have any problems.

So the short answer is I don't think there will be a fix soon, but maybe in a future update.

Regards

Paul

Unknown said:

The idea behind merging is working in a single file (to make life easier I guess). What is the point of being able to merge files, edit them, and then having no way to update the original single files?

Hi Spiros Doikas of course I agree and you could achieve this by using the merge in the project after you created it rather than merge them before.  In fact you remove all possibilities of handling them any other way at all if you merge them beforehand.  However, I think this is something we already know about but it doesn't have a high priority to resolve, mainly because the process works perfectly for non-sdlxliff files and you have a workaround by using what many would consider a better solution anyway by merging them after the project is created and then you won't have any problems.

So the short answer is I don't think there will be a fix soon, but maybe in a future update.

Regards

Paul

Heh, so typical...

Yet another half-baked "feature" with apparently missing rationale behind, but without any real chance to get fixed because "there is a workaround" (and no one cares how illogical this workaround could be... yes, it IS illogical... as opposed to intuitive and logical common-sense assumption that if something is merged at the beginning, there should be the reverse un-merging possibility at the end).

Get some (originally good) idea, then cripple it by taking only half of it (like, implementing both loading AND saving files would cost too much... let's implement only loading...), then cripple it further by terrible implementation (e.g. alignment editor or impossibility to create merged file AFTER project is created), then add A LOT OF MARKETING HYPE, so that everybody takes out his wallet... and then just abandon it and start this process again with some other idea...

Who cares about all the betrayed users indefinitely waiting for fix...

Hi Spiros Doikas of course I agree and you could achieve this by using the merge in the project after you created it rather than merge them before.

Not sure what you mean by this or how it can be done. I merge them at project creation, just after adding the files. I do not see any other option to merge once the files have been added and the project wizard has been completed. Would you care to explain? Of course, I am always talking about sdxliff files that I want to edit.

At the very least, the system should not allow one to merge the files in the first place, if unmerging is not an option! This is like a woman inviting you to bed, and as soon as you get there you get a kick in the teeth.

Hi Spiros Doikas 

Unknown said:

I do not see any other option to merge once the files have been added and the project wizard has been completed. Would you care to explain?

Of course... it's probably easier than you think.  You just select the files you wish to merge in the Files View and open for translation.  This will merge them together in the Editor in the order you selected them.  It's not a permanent merge, so the sdlxliff files you selected do not become one file that you could then send to others but they will all open as if they were one file in the editor.