The issue had been fixed and delivered with Passolo 2018 CU3

Hello Achim Herrmann and Florina Paduraru,

what does fixed mean here? We're working with 2018 Version 18.0.133.0 and it seems that only if the strings are hidden they are excluded from export. Correct? I'd need to see the strings in Passolo some cases, so it's not the ideal solution in my case.

I'd rather thought the XLIFF export settings would be refined so I can define there whether or not to export the strings. While we're on that topic: Would also be helpful to be able to export strings "in review" , for expample, in some cases...:-)

Thanks

yve

Fixed means that hidden strings are not exported while read-only strings are exported as locked content that can't be editied in Studio.

So the approach is quite similar to what translator experience when editing in SDL Passolo

Fixed means that hidden strings are not exported while read-only strings are exported as locked content that can't be editied in Studio.

So the approach is quite similar to what translator experience when editing in SDL Passolo

thank you, Achim Herrmann,

The thing is, we cannot hide all locked strings because then we got problems with resizing the dialogs in the old dll versions and also I want the strings to be there as reference texts in Passolo.

Do you have any idea how we could handle that? Translators sometimes have 80% "locked" strings and 20% really to translate - but the statistics also do not reflect that. I also do not get these strings as "locked segments" in Trados -so I don't see a way to filter the display or something. Then I could maybe already set all these strings to translated or something - which,however, in turn, will blow up the TM with useless technical stuff ..:-(

I still think that it would be great if there was an option during export whether locked / hidden strings should be excluded...