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
Language Technology Partner Group
SDL Academic Partners
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
To SDL Training
Training & Certification
What's New in SDL
Detecting language please wait for.......
I am working in a specific XML type:
<Value AttributeID="Colour">foo</Value> <Value AttributeID="Size">foo</Value> <MultiValue AttributeID="CODE">
I designed a custom XML file type, with parser rules that work fine, except for the Document Explorer. In the Document Structure pane of the Editor, I want to show a hierarchical view:
[Product ID value]
In other words, I want to use the value of the Product element's ID attribute. I can easily come up with an XPath and put it in the parser rules. However, Studio doesn't take the value (e.g. 2112570), but the name of the attribute (e.g. Product ID).
I'd think this would work, but it doesn't:
I found another user on this forum who managed to do it, but I don't understand his solution: https://community.sdl.com/product-groups/translationproductivity/f/studio/8664/display-element-content-in-document-explorer-in-studio-editor
Any help would be appreciated!
Hi Ken De Wachter, Ken De Wachter
Allow me to campaign for my idea about XML DSI at this place: https://community.sdl.com/ideas/translation-productivity-ideas/i/trados-studio-ideas/enable-more-document-structure…
Ken De Wachter said:Thanks for your response. I managed to configure the Document Structure column without many issues. It's a relatively easy and powerful feature. However, having to click it every segment…
Hello Ken De Wachter ,I hope I can:As far as I know, in what is called "Editor view navigation pane", only text nodes of XML documents can be made visible.On the other hand in the popup that can be opened from the "Document Structure column", you can visualize virtually everything:text nodes, attribute values, XML comments and even content of processing instructions.I hope this is the answer you were looking for.
Thanks for your response. I managed to configure the Document Structure column without many issues. It's a relatively easy and powerful feature. However, having to click it every segment to see the product ID is a bit of a drag...
In the post I refer to, it seems like you found a solution 3 years ago:
thanks for your reply. I was on the wrong track. The way to obtain the values I want, is to define parser rules for "Name" elements (translatable and non-translatable ones) and then it is possible to have the names displayed in the Document Explorer. And if I want to see both the hierarchy of products and the names, I need to enable "ShowElementContent" for both elements.
Any clue what you meant by that? (c:
Ken De Wachter said:Thanks for your response. I managed to configure the Document Structure column without many issues. It's a relatively easy and powerful feature. However, having to click it every segment to see the product ID is a bit of a drag...
Ken De Wachter
Why not install this plugin?
Takes the drag out of it ;-)
What I meant three years ago is the following:If you want to display text node content in the "navigation pane", you need to define a parser rule for the specific element, even if this parser rule is not needed for anything else, since this element is supposed to be handled in the Studio default manner (structure and not inline / translatable unless "not-translatable" is inherited from higher hierarchical level).(You will probably know that defining XML parser rules (for a specific element) is only needed, if the node should be handled in a non-default way.)In the "Document Structure Information" column on the other hand, you are able to extract XML content from a completely different part of the XML document using relative XPath statements that allow you to extract virtually whatever XML node you are interested in.
That was plan B, which just became plan A (c:
Thanks for the help Paul and Frank!
You'll enjoy the new version of the Community Advanced Display Filter too as this adds excellent filtering capability by supporting a search within any of the fields in the DSI pane.
Allow me to campaign for my idea about XML DSI at this place: https://community.sdl.com/ideas/translation-productivity-ideas/i/trados-studio-ideas/enable-more-document-structure-information-when-using-the-embedded-content-processor
You are obviously not using the embedded content processors, otherwise the above solution would not work for you. But: The ECPs are a really cool feature - just they strip all parsing data, so you can't have any context information gleaned while parsing.
My hope is that this will be addressed at some point, as the workaround is a bit laborious.
Daniel Hug said:My hope is that this will be addressed at some point, as the workaround is a bit laborious.
Mine too... would be good to see more votes for this idea.