Allow combination of Embedded HTML content processing with other XML filter features in XML 2.0 filter

Currently, the new XML 2.0 filter has limitations, if I want to take advantage of the HTML Embedded Content Processing. I am not able:

to show to the translator/reviewer which HTML block corresponds to which text type (for instance "short description" or "long description") via DSI metadata
to tell the translator that character-based length restrictions apply to certain HTML blocks, not only plain-text blocks
to show an interactive preview for HTML blocks inside Studio, whereas Trados Enterprise allows this.

My XML document:

XML code snippet showing product descriptions with 'Product title', 'Short description', and 'Long description' elements.

shows as follows in Studio:

Trados Studio interface displaying the translation of 'Product title', 'Short description', and 'Long description' without a preview available.

Frank Lempp

Top Comments

Frank Lempp over 2 years ago in reply to Paul Filkin +1

Hello Paul Filkin , the issue is that if your cursor is in a segment that is handled by an external Embedded Content Processor like the HTML one, the preview window pane will tell you "There is no preview…

Paul Filkin over 2 years ago in reply to Paul Filkin

In fact I'd already voted!! I'm feeling the age creeping in!!
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Paul Filkin over 2 years ago in reply to Paul Filkin

Frank Lempp Daniel Hug

I see now... thanks for the extended explanation! Definitely gets my vote!
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Frank Lempp over 2 years ago in reply to Paul Filkin

Hello Paul Filkin ,
the issue is that if your cursor is in a segment that is handled by an external Embedded Content Processor like the HTML one, the preview window pane will tell you "There is no preview available".
The issue becomes serious if all segments are handled this way, since even if the preview is configured, you will not able to able launch it.
Documents where both plain-text and HTML-text text blocks are embedded inside CDATA sections are the most likely documents for this issue.
Studio will not allow to launch a preview.
- Cancel
- Vote Up +1 Vote Down
- More
- Cancel
Paul Filkin over 2 years ago in reply to Daniel Hug

Daniel Hug

The ECP and the legacy embedded content processors are not dependent on the preview in any way. I don't really understand your point there.... probably I'm still misunderstanding you. But irrespective of the processor used to handle embedded content you can still create the preview for whatever you like. Perhaps create a post in the forum (if you didn't already) and explain the problem here?
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Daniel Hug over 2 years ago in reply to Paul Filkin

Paul Filkin I can use custom XML previews only with the legacy embedded content processor. The ECP does not have any preview option.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel

Trados Portfolio Ideas > Trados Studio Ideas

Allow combination of Embedded HTML content processing with other XML filter features in XML 2.0 filter

Top Comments