SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
we have defined an xml filter for our specific CMS files (GRIPS) but are not able to let show some "context information" as it is possible in SDL Studio.
We had already a filter which works correctly in SDL Studio. We have exported the settings and imported them in WorldServer. We first noticed that the rules were not sorted like in Studio - but from the last rule to the first rule. After changing this, we were still not able to see the information.
We have also generated a package to be open in Studio. In Studio, no surprise, the information are not in the sdlxliff. But when I prepare the same source file in this project, then the preparation works as expected. It looks like as WorldServer does not write the information in the sdlxliff whereas Studio does.
Is it a known bug? Has anybody noticed that? Or is it not implemented yet?
We use the version 10.4.2.
Is the context information that you are talking about like the aqua 'M' in the image below?
If so, i think i can help. You can configure that in WS by clicking advanced on any given parser rule
Then clicking the edit button on the structure line
Then adding a new property
You can use predefined ones from the dropdown and can also create your own.*Note there is a bug i already have raised with SDL where if you do not change the color before selecting something else in the drop-down, you are unable to change the color until you save and then re-open the property for editing. I also suggested in the same ticket that the default color be something other than black (which is not very helpful)
Once it is saved you can then edit what you want to show up in the document explorer, the context name or the content in the context.
If this is not what you are talking about can you clarify what it is?
Hi Eric, so we got the answer: it's a bug in WorldServer. We had 3 rules in our XML parser: //TAG[@Name=AUFGABE] with AUF as context info //TAG[@Name=ANWEISUNG] with ANW as context info //TAG (for the other Names) With this configuration WS is not able to set the context info. But without the rule "//TAG", it works. Fortunately, it was OK for us to remove it and we have what we need. Kind regards Sébastien