You are currently working on UAT 

  • State Verified Answer
  • Replies 1 reply
  • Subscribers 430 subscribers
  • Views 658 views
  • Users 0 members are here
Options
Related

Merge files at project creation vs. virtually merging them later

Daniel Hug

I looked a bit more into merging files at project creation, and I must correct myself (https://community.sdl.com/product-groups/translationproductivity/f/studio/27878/exporting-merged-incopy-files/88997#88997) that it is indeed possible to "unmerge" using the "export files" batch function.

My wonderment is: Why both options? Is there a historical reason for that? (E.g. merge at project creation was introduced first and is still part of the program as kind of legacy functionality.) Virtual merge seems much more pwerful and flexible, but I might be missing out on something?

Daniel
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • +1

    Yes, there is a historical reason. The physical merge existed (way?) earlier than the virtual merge.

    The advantage(?) of physical merge is that the creator of the merged SDLXLIFF is in control of WHAT will be merged and in which ORDER it will be merged... and that these are not changeable during the translation process.

    The biggest disadvantage is that Studio is unable to use various functionality with (merged) SDLXLIFFs, such as splitting to multiple translation packages - Studio is unable to split at finer granularity than entire SDLXLIFF, i.e. you can't use merge (e.g. to enforce translation in certain files order) and split (to allow parallel translation by multiple translators) at the same time :(