Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
Hello. I love the new functionality to export SDLXLIFFs from Passolo 2018. I've noticed that Read-only strings in Passolo (and possibly Hidden strings as well?) are output as translatable segments in these SDLXLIFFs. I wonder if this should be updated to output these strings as locked or even not extracted?
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 184.108.40.206 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...:-)
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...
Hello Florina Paduraru,
Do you maybe have an idea to my question below?
It's really annoying for us at the moment because we lock the strings in Passolo so we can get them out of translation but then we have to pay for them because altough they cannot be edited, they do not appear as locked strings in the Trados analysis :-(
If you lock the strings in the target string list then they will show as locked in Studio editor view.
As for the Analyze task you need to enable the option Report Locked Segments Separately. After this the report will have an additional entry for the locked segments.
Hope this helps.