Hi,

no it's not possible via the parser rules as the content you need to display is attribute value. XML filter doesn't extract attribute value unless it's set to translatable.

In my opinion much better and more flexible way would be to create a custom preview which will display the instructions for the particular part of the extracted text - this can be achieved by using the API and plug-in the new component into existing XML filter.

Regards

Patrik

Hi Patrik,

thank you for your quick reply.

We already created and shipped a custom preview for this type of documents. But the preview is rather considered a temporary solution, since the translators are used to TagEditor and would expect this to be the same in Studio, justifying it with reasons of cost.

Is there any other way how the translators can see which section they are translating (similar to TagEditor)?

Thanks again

Simon

Not that I'm aware of - out of the box.

Why the translators think the preview doesn't give them what they need? Why it would be any different? I would consider it as improvement as it can clearly identify instructions even if they work with very long sections where in TagEditor it would be a pain to search for that one tag.

Patrik

I basically agree, since this is, what I originally proposed to them, too.

They say, "If we do not have the same easy display in the new solution, I would consider this is a step backwards."

The section headers have to be displayed, so that the translators know, where they are translating. But the headers have to be locked for cost reasons. And the preview is not sufficient, since consuming it takes time, which would cause additional costs.

So there is no good solution for their issue at all?

Thanks

Simon

One more question: Would it be possible to "develop" a custom file type which takes these non-translation-relevant attribute values into account or is there really no solution other than endeavouring to persuade them to use the preview?

Thanks again

Simon

Maybe they could use the display filter to work with All Content, instead of All Segments?  It may be messy, depending on the structure of the XML but it had worked for others in the past.

But I'm with Patrik on this.  The use of a stylesheet is much better.  It's probably just a mindset they need to get used to.

Regards

Paul

Hi,

Pardon me for barging in. There's one instance that I can think of where being able to see the attributes in the text but locked would be useful. If the reviewers wants to see such information when they review the exported Word files, that would be the only way to see such information. I have a client that requires this.

Tak

Hi,

This would be going out of your way, but you could do this.

In the XML file, do a search and replace on all relevant attribute values to include an identifying string in the value.

Example:

Replace

<section id="02" title="Weitere Begriffe">

with

<section id="02" title="##title##Weitere Begriffe">

Then, configure the file type parser so that this attribute is read in as translatable.

In Editor, open the file, and use the filter to search for segments that include "##title##".

Lock them.

After translating and generating the translated XML, do another search and replace to take out the identifying string.

Regards,

Tak Osato

Hi,

This would be going out of your way, but you could do this.

In the XML file, do a search and replace on all relevant attribute values to include an identifying string in the value.

Example:

Replace

<section id="02" title="Weitere Begriffe">

with

<section id="02" title="##title##Weitere Begriffe">

Then, configure the file type parser so that this attribute is read in as translatable.

In Editor, open the file, and use the filter to search for segments that include "##title##".

Lock them.

After translating and generating the translated XML, do another search and replace to take out the identifying string.

Regards,

Tak Osato