Hi Daniel Hug

Please see this screenshot below, this is where the context information (as structure detail) and the comments are visible in Editor view:

(By clicking on the last column in the Editor view, next to the target translation column.)

The source file looks like this so you can see where the details are coming from in the bilingual Excel:

Let me know if you can see these details in your Studio as well.

Best wishes,

Greta Magyar
Customer Success Representative - SDL

Hello Daniel Hug

As for the comments, I don't think you can change the severity, and I just checked it again but to be honest I could not find a way to do that.

Regarding the context, it has nothing to do with the embedded content. I just specified which column contains the context info I would like to make visible in Studio, please see my settings below:

Happy to take a look at your settings if you can share them here, or if not please send me an email with the screenshot at gmagyar@sdl.com 

Best wishes,

Greta

Just for future reference, as discussed with Daniel there is a Studio app which displays the comments in a dynamic way, the Segment Information Viewer: https://appstore.sdl.com/language/app/segment-information-viewer/865/

When you move down a segment the window will automatically show the corresponding comments and further information on the segment (no. of characters, etc.):

But first the comments information has to be specified in the Project settings as detailed above and the plugin should be enabled on the ribbon in the Editor view:

Greta

Thank you for all your help. As for the problem with context information not being displayed, this was not solved in this thread, but in this.

(It seemingly has to do with XML maps stored in the Excel file.)

Daniel

Hi Robert Bevington 
I overcame this problem by removing the XML Map from the Excel file. You will have to remap it once the translation is done, but this way your translator can see the context. I also fully agree with your statement that with (monolingual) XML files the context information display should be improved when the embedded content processor is used. I started an idea about this, please support it: community.sdl.com/.../enable-more-document-structure-information-when-using-the-embedded-content-processor
As for bilingual XML files, I only sometimes use the bilingual XML [edit] Excel [/edit] file type for this because if one XML node contains a substantial amount of text the TM is almost useless - this is not a Trados-specific problem. Content of such nodes would have to be aligned automatically or manually in order to become useful. So with bilingual XML files I tend to first align them, then only import the source language and do a perfect match. I unlock those perfect matches and "demote" them from "signed off" to "translated".
There is also the possibility of converting the bilingual XML to XLIFF using the Okapi toolkit, but that is not exactly straightforward and I have not had time and/or incentive enough to really develop a smooth process here.

Let me know whether removing the XML map solves the problem for you.
Daniel

Hi Robert Bevington 
I overcame this problem by removing the XML Map from the Excel file. You will have to remap it once the translation is done, but this way your translator can see the context. I also fully agree with your statement that with (monolingual) XML files the context information display should be improved when the embedded content processor is used. I started an idea about this, please support it: community.sdl.com/.../enable-more-document-structure-information-when-using-the-embedded-content-processor
As for bilingual XML files, I only sometimes use the bilingual XML [edit] Excel [/edit] file type for this because if one XML node contains a substantial amount of text the TM is almost useless - this is not a Trados-specific problem. Content of such nodes would have to be aligned automatically or manually in order to become useful. So with bilingual XML files I tend to first align them, then only import the source language and do a perfect match. I unlock those perfect matches and "demote" them from "signed off" to "translated".
There is also the possibility of converting the bilingual XML to XLIFF using the Okapi toolkit, but that is not exactly straightforward and I have not had time and/or incentive enough to really develop a smooth process here.

Let me know whether removing the XML map solves the problem for you.
Daniel