Most probably you have received the translation as package and your PM has deactivated this option.

Even if it would be possible to change that, you should not really do that. Merging segments over paragraph breaks can be really dangerous. The structure of the target file can be seriously damaged, depending on the file format.

Before I tell you how to circumvent this, please tell me the file format you are translating. Are there tags in the segments you want to merge?

Hello Jerzy and thank you

Yes, changing this might be dangerous... But not doing so is polluting my TM with mixed translations for some specific and important terms :/

I'm working with PPT files. The specific segments I need to merge have no tags and contain just 1 word each (they work together, but have to be translated the other way round from German to French).

I would love to learn how to force a merge in this case!

Ingrid

For PPT it should work and I know your problem very well. If the segments are subsequent, you can indeed merge these—provided the words in question are not located in a table.

The easiest way to circumvent this issue is the following:

• Start creating your own project with proper resources (TM/TB)
• Instead of the source PPT take the sdlxliff file(s) from the target folder of your received package and use these as source files
• Complete the project creation
• Make sure merging segments is activated
• Translate as usual
• After merging segments try to save target and to open the target file
• If that works, continue
• Should this not work, do not save your sdlxliff file, close without saving
• Reopen the file for translation, however do NOT merge segments now, as this caused problems—translate these instead "as is", but do NOT confirm these segments, just change the status of those to "Sign-off rejected" and lock them; this way they won't update and mess up your TM
• When finished, simply copy the sdlxliff file(s) from the target folder of your project and paste these into the target folder of the customer package
• This will overwrite the files in the target folder of the package—this is indeed desired
• Run the "Translation count" batch task in the customer project
• Create the return package

Or simply ask the PM to activate the settings and send a new package

For PPT it should work and I know your problem very well. If the segments are subsequent, you can indeed merge these—provided the words in question are not located in a table.

The easiest way to circumvent this issue is the following:

• Start creating your own project with proper resources (TM/TB)
• Instead of the source PPT take the sdlxliff file(s) from the target folder of your received package and use these as source files
• Complete the project creation
• Make sure merging segments is activated
• Translate as usual
• After merging segments try to save target and to open the target file
• If that works, continue
• Should this not work, do not save your sdlxliff file, close without saving
• Reopen the file for translation, however do NOT merge segments now, as this caused problems—translate these instead "as is", but do NOT confirm these segments, just change the status of those to "Sign-off rejected" and lock them; this way they won't update and mess up your TM
• When finished, simply copy the sdlxliff file(s) from the target folder of your project and paste these into the target folder of the customer package
• This will overwrite the files in the target folder of the package—this is indeed desired
• Run the "Translation count" batch task in the customer project
• Create the return package

Or simply ask the PM to activate the settings and send a new package

Thank you so much Jerzy!

I'll try this with a project that is already finished and delivered - should avoid any desaster ;)

There will be no disaster, if you follow these steps

I use this method since Studio exists, not only because of merging segments, but mainly because I use my own project templates with many individualized settings. It is faster than to adapt all these settings within a customer package.