6 now so this is clearly not going anywhere fast but it's a major pain in our backside because a lot of the FOSS projects I participate in rely on the po format.

Is there some dirty segmentation hack that might work to "merge" the pieces in Trados? Something that parses " + linebreak + " into something that doesn't appear in the strings but that allows me to create a valid po output file?

Michael Bauer have you tried using the one on the appstore?  I have not tested it but perhaps it has more options for you:

https://appstore.sdl.com/language/app/file-type-definition-for-po-extended/868/

Hi Michael Bauer,

even if this thread is a bit older, I had the same issue a few weeks ago whereas I had one job where 1 Segment from po file had 2000 words (a whole contract in 1 segment) :((( I used the following work around, although certainly not the best (as you'll have to do it file by file) but it worked:

Select the file in Trados project and immediately create a bilingual file for review (export for review).

In that docx file select the source strings without the header, copy paste to a new word file and prepare and translate that file. It should get correctly segmented due to Word format.

After you're done and have reverted sdlxliff back to Word, copy paste the translated strings into the source column of the review export and import it back via batch task.

Open the file in review mode and accept all changes. You should now have a fully translated po file.

Hi Michael Bauer,

even if this thread is a bit older, I had the same issue a few weeks ago whereas I had one job where 1 Segment from po file had 2000 words (a whole contract in 1 segment) :((( I used the following work around, although certainly not the best (as you'll have to do it file by file) but it worked:

Select the file in Trados project and immediately create a bilingual file for review (export for review).

In that docx file select the source strings without the header, copy paste to a new word file and prepare and translate that file. It should get correctly segmented due to Word format.

After you're done and have reverted sdlxliff back to Word, copy paste the translated strings into the source column of the review export and import it back via batch task.

Open the file in review mode and accept all changes. You should now have a fully translated po file.

Hi Pascal. Thanks for taking the time to respond

Yeah, in a case like yours, where there's a single (or a few) segments of such crazy length, that workaround works (although if it was only a few segments like that, I'd probably just copy and paste the text into Word and then back again after translating). But unfortunately that doesn't work when you have thousands of segments.

Hi Michael,

Yes, but if you have tags in the segments, a simple copy paste will not do as you'll not get the tags. That's why I opted for the review export. I'm trying to find/program a better solution though but that can take some time.

Fair point.

The bizarre thing is, they claimed the "idea has been delivered". 

Paul how come it says "delivered" and it's still not working, any thoughts?

One for Daniel Brockmann or Patrik Mazanek I think.  

Could you upload a sample file, Pascal Zotto?

The change was already delivered, it might not get to Studio yet, but for sure will be with SR2 release.

Any section without translation will be segmented.

Then perhaps the "Delivered" button shout be expanded with the release number in which something was or will be delivered? Crazy idea, I know ... it'd be like putting out a ferry timetable saying "Winter timetable from [date]" instead of just hanging up the winter timetable in July ...

The functionality was available in other products which have different release cycle as Studio much earlier - e.g. in Trados Live for any online project created it would be already available for several months.

And who outside the matrix knows that?