Hi everyone, I'd like to easily merge multiple project files which were not merged when the project was created. I use this as a basis for creating a source/target printout I can read efficiently. So far: Split/Merge app doesn't work for Studio 2017 SDLXLIFFToolkit merge resulted in a corrupt merged SDLXLIFF I'd use Export for External Review however this produces a word document for each project file The 'good bug' ( https://multifarious.filkin.com/2015/12/11/good-bugs-bad-bugs/ ) in Studio 2015 that produced a termporary file for virtually merged files seems to have been fixed in Studio 2017 (zip files are produced during then merge and deleted I'd love to be able to create a merged SDLXLIFF whenever I need by virtually merging the file and saving the virtual merge result as an SDLXLIFF but short of that does anyone have any idea of the best solution here aside from merging the files at the start of the project (which can't be done if someone else creates the project packages)? I guess one way is creating another project with the files merged and then using PerfectMatch to pretranslate but it's longwinded. I don't need to use the merged SDLXLIFF for saving target files, I just need it for easy reading. Many thanks, Daniel

What is the reason for doing that? In fact having the files merged physically is more problematic than opening them in virtual merge as needed. As for your question: AFAIK the only way to merge files physically is create a new project, where you can add any kind of ile, including already created sdlxliff files.

Studio 2017: how to merge project files into one SDLXLIFF after a project has been created?

Daniel McCosh over 8 years ago

Hi everyone,

I'd like to easily merge multiple project files which were not merged when the project was created. I use this as a basis for creating a source/target printout I can read efficiently. So far:

Split/Merge app doesn't work for Studio 2017
SDLXLIFFToolkit merge resulted in a corrupt merged SDLXLIFF
I'd use Export for External Review however this produces a word document for each project file
The 'good bug' ( https://multifarious.filkin.com/2015/12/11/good-bugs-bad-bugs/ ) in Studio 2015 that produced a termporary file for virtually merged files seems to have been fixed in Studio 2017 (zip files are produced during then merge and deleted

I'd love to be able to create a merged SDLXLIFF whenever I need by virtually merging the file and saving the virtual merge result as an SDLXLIFF but short of that does anyone have any idea of the best solution here aside from merging the files at the start of the project (which can't be done if someone else creates the project packages)?

I guess one way is creating another project with the files merged and then using PerfectMatch to pretranslate but it's longwinded. I don't need to use the merged SDLXLIFF for saving target files, I just need it for easy reading.

Many thanks,

Daniel

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Studio 2017: how to merge project files into one SDLXLIFF after a project has been created? Hi everyone, I'd like to easily merge multiple project files which were not merged when the project was created. I use this as a basis for creating a source/target printout I can read efficiently. So far: Split/Merge app doesn't work for Studio 2017 SDLXLIFFToolkit merge resulted in a corrupt merged SDLXLIFF I'd use Export for External Review however this produces a word document for each project file The 'good bug' ( https://multifarious.filkin.com/2015/12/11/good-bugs-bad-bugs/ ) in Studio 2015 that produced a termporary file for virtually merged files seems to have been fixed in Studio 2017 (zip files are produced during then merge and deleted I'd love to be able to create a merged SDLXLIFF whenever I need by virtually merging the file and saving the virtual merge result as an SDLXLIFF but short of that does anyone have any idea of the best solution here aside from merging the files at the start of the project (which can't be done if someone else creates the project packages)? I guess one way is creating another project with the files merged and then using PerfectMatch to pretranslate but it's longwinded. I don't need to use the merged SDLXLIFF for saving target files, I just need it for easy reading. Many thanks, Daniel
Get AI Suggestion

AI Reply

Accept answer Reject Answer

0 Jerzy Czopik over 8 years ago

What is the reason for doing that?
In fact having the files merged physically is more problematic than opening them in virtual merge as needed.
As for your question: AFAIK the only way to merge files physically is create a new project, where you can add any kind of ile, including already created sdlxliff files.

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Daniel McCosh over 8 years ago in reply to Jerzy Czopik

Thanks Jerzy, I forgot you can add sdlxliff files to a new project. There are situations where I need a printout of an entire project 1) occasionally for myself 2) for professors who are reviewing manuscripts in many chapters and wish to work that way.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 8 years ago in reply to Daniel McCosh

So adding SDLXLIFF files to a new project and maybe removing then from there as needed will be the solution here.
TBH I only use virtual merge now, as this more convenient for working. However, when I would need to have several files externally revised via bilingual Word file, merging physically would certainly be better.

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 8 years ago in reply to Jerzy Czopik

Unknown said:
What is the reason for doing that?
In fact having the files merged physically is more problematic than opening them in virtual merge as needed.

For example I had a need to keep individual files in particular order, so that they follow certain 'logical' order. The files come from e-learning course, i.e. there are many various original formats (Articulate, Flash, Word, etc.) and therefore need to retain their filenames (so achieving the logical order by e.g. putting a number in front of the filename is a no-go... if not for anything else then because I'm not interested in renaming dozens of files in 20+ target languages...).

This is precisely a task for files merge...
Unfortunately it's a one-off action, which can only be done at the project creation time... yet another originally good idea, but left terribly unfinished :(

Virtual merge is basically useless from engineering perspective... but no one seems to realize that not only translators work with Studio...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 8 years ago in reply to Evzen Polenka

Or you select the files in the file view in the order you want to open them by keeping CTRL pressed and clicking the files one by one. This is precisely a reason for not merging them :)

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 8 years ago in reply to Jerzy Czopik

You don't understand - I'm ENGINEER, not translator... I'm preparing projects/packages for translators.
And no, I CANNOT rely on translators either knowing these tricks, or following instructions... this has NEVER worked in my entire localization career since 1999.
EVERYTHING MUST be prepared fool-proof on our side... NEVER trust translators...
Sorry if this offends someone... just expressing my long-term experience.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 8 years ago in reply to Evzen Polenka

Yes, it does offend me. I am an engineer and a translator :)

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Nora Díaz over 8 years ago in reply to Evzen Polenka

Unknown said:

NEVER trust translators...

That's a little harsh...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 8 years ago in reply to Nora Díaz

I'm sorry, but as I said, that's my long-term experience. I'm not happy about it at all, believe me... but I cannot influence which translators work on the projects.
And, unfortunately, vast majority of translators was not able to follow the simplest instructions... way too many of them even don't know some elementary Studio functionality... I'm pretty sure it has actually a lot to do with their rates - there is a push on using the cheapest possible suppliers and, as we know, "you pay peanuts, you get monkeys"...
Well, I can work only with what I have... so I have to prepare everything really "stupid-proof"... and if I omit something, it strikes VERY strongly back...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 8 years ago in reply to Evzen Polenka

So you pay peanuts... Now I understand.

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Studio 2017: how to merge project files into one SDLXLIFF after a project has been created?