HTML tags embedded in XLSX and XLIFF files are not visualized correctly in the Editor view even when the “Enable embedded content processing” option is enabled (Studio 2019)

Question

Hi, there!

I am having a very difficult time with a couple of documents (hope you can help me sort it out!).

I processed xlsx and xliff files with html embedded content. I ticked the “Enable embedded content processing” but, since that was clearly not enough in itself, I checked the forum and found out that RULES had to be added and document STRUCTURES had to be defined:

So I did it for both file types (see image)

Trados Studio settings showing 'Enable embedded content processing' checked with document structure information defined for sdl:data, sdl:cell, and sdl:html-control.

Reference links:

community.rws.com/.../136471

gateway.sdl.com/communityknowledge

The tags were visualized correctly in the “Preview” option, even before adding rules/structures (and they still are now):

Preview window in Trados Studio displaying text without visible HTML tags, indicating correct processing of embedded content.

However, they were/are shown with the <p> </p> format the Editor view (see image), which is what I trying to avoid.

I am not sure what is missing.

Generated Image Alt-Text
[edited by: Trados AI at 3:13 PM (GMT 0) on 1 Mar 2024]

format the Editor view (see image), which is what I trying to avoid. I am not sure what is missing.

Paul · Answer

Paola Petrocelli 
 Most likely your rules are not correct. Looking at what you have used I suspect you tried to do something with what was the default suggestion and you probably have some overlap somewhere. I'd be inclined to use the Multilingual XML filetype for the XLIFF if you need to handle embedded content, and if the Excel is also multilingual I'd use the Multilingual Excel filetype too for at least the same reason. 
 Multilingual XML FileType 
 Multilingual Excel Filetype 
 If you can't then maybe provide a couple of small sample files that represent the layout of your file and we can have a go at helping you with improved rules.

Jerzy Czopik · Answer

Paola Petrocelli 
 Your rules are far to general. It is much more advisable to have a separate rule for the p, b, br, a href and other tags. This way you can much better fine tune the output and do not risk overlapping.

Paul · Answer

Paola Petrocelli The rules are created using regular expressions. It's worth you learning a little about this syntax as it's useful in many applications. Most CAT tools use them, decent text editor use them and they can be very powerful. Often the syntax is nothing more than plain text and for your rules that would most likely be the case. The rules you used were catch all rules designed to try and pick up everything, probably as a placeholder. You need opening and closing tags, for example (and in plain text):

Some text in here...

The opening tags rule would be:

The closing tag rule would be:

Similarly for some of the ones you showed in your screenshots:

If there are many non-translatable attributes in the element like this: Some translatable text here Then in this case you would need to use proper syntax if you don't want to write out every possible attribute type that might be in the file. For example: ]+?> So for the opening tag the syntax would mean: ] This means find any character apart from a > +? This means find as many of the characters you were looking for as you can but only keep finding until you find the first > that you were looking for > Plain text again So not too tricky and once you start using them you'll feel more comfortable to create your own more complex things. Regular expressions are not a Trados thing so you can search and find information all over the internet for this. Important thing to remember is there are many flavours of syntax. We use C# (.NET) flavour.

Trados Studio > 1. Trados Studio

HTML tags embedded in XLSX and XLIFF files are not visualized correctly in the Editor view even when the “Enable embedded content processing” option is enabled (Studio 2019)