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.

Regards

Frank

Hi Frank,

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:

Hi Frank,

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?

https://appstore.sdl.com/language/app/dsi-viewer/995/

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.

Hi Paul,

That was plan B, which just became plan A (c:

Thanks for the help Paul and Frank!

Best,

Ken

Ken De Wachter

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.

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-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

Unknown 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.