Gilberto V.V.

You can handle these files using Studio, in a variety of ways.  The easiest is probably to use the embedded content processor, like this:

That will get you something like this:

And of course you could expand the tag so it's still readable if needed:

As always, Paul. Thank you very much!

First time I'm using this option.

A couple of questions:

It's not very clear from the image: It looks like "<%,+?%>" (comma after %). I tried that (and a period too) but it doesn't work. Could you please tell me what's the correct text?

I believe I'm OK by choosing "sdl:body" for the Document structure information.

I'm just afraid the tags generated through this method may not coincide with the ones contained in our TM (all files have been processed with the programming text blocked). We shall see.

Thanks again.

As always, Paul. Thank you very much!

First time I'm using this option.

A couple of questions:

It's not very clear from the image: It looks like "<%,+?%>" (comma after %). I tried that (and a period too) but it doesn't work. Could you please tell me what's the correct text?

I believe I'm OK by choosing "sdl:body" for the Document structure information.

I'm just afraid the tags generated through this method may not coincide with the ones contained in our TM (all files have been processed with the programming text blocked). We shall see.

Thanks again.

Gilberto V.V.

Gilberto V.V. said:

It's not very clear from the image: It looks like "<%,+?%>" (comma after %). I tried that (and a period too) but it doesn't work. Could you please tell me what's the correct text?

<%.+?%>

I think the reason the period failed for you is either because of the next point or because your actual file contains something different.

Gilberto V.V. said:

I believe I'm OK by choosing "sdl:body" for the Document structure information.

You should use what I suggested as it's a catch all.  If you don't you have to make sure you identify all the different sorts of structure that could contain this text.

Look at Paul's screenshot. He does not use any specific structure information, but the option "Extract in all paragraphs". This is IMO the culprit here. And of course you need to create this rule in your project template BEFORE adding any files to the project. If you do that afterwards, it won't work.

For resolving this issue in an already created project, use Cleanup Tasks.

Thank you, Paul!

I'm using Trados Studio 2021 and I don't get those two options ("Extract in defined. . ." and "Extract in all. . .".  I just get "Document structure information".
I'm still unable to convert to tags. Will keep trying.

Thanks again.

Gilberto

Are you possibly using a project template, which has been created in an older version of Studio? If so, click the "Reset to default" at the bottom of the file types view.

Gilberto V.V.

Make sure you have this version:

SDL Trados Studio 2021 - 16.0.2.3343
SDL MultiTerm 2021 - 16.0.1.304

I have a feeling this may have been introduced recently as it was available in Trados Live but not Studio.

The version I have is 16.0.1.2917.

I got it to work for some instances by changing to "sdl:paragraph".

Unfortunately the different kind of tags (the ones from this method and the ones we have in TM ("ContentControl" created by blocking text) create matching issues.

I'm not sure if that can be easily resolved.

Gilberto V.V.

First: upgrade to the version Paul mentioned.

Second: post examples of text to be hidden. Regex is very flexible and Paul (or some other people here) will be able to provide solutions.

But for the time being the first step is to upgrade. Or you just add all possible options for document structure, like sdl:paragraph, sdl:heading and so on, as you cannot tell upfront in which parts of your files the tags will occur.

Gilberto V.V.

Gilberto V.V. said:

I got it to work for some instances by changing to "sdl:paragraph".

That's because some of your texts have the paragraph structure, but not all.  You either upgrade (it's free!) or add the appropriate structure for every instance in your file.

Thank you, Jerzy, for your input and comments. In my original posting I have added two sample files.

Thank you, Paul, for your comments and advice.