Hi Javier,

You won't be able to convert the entities but you can protect them as placeholder tags using the embedded content processor. Try this as a catchall... think it will get most:

&\w+;

If you want to go the other way then this won't be possible at all... you'd have to write the entities themselves.  I guess you could do that with quick inserts, or maybe using autocorrect perhaps?

Regards

Paul

Hi Javier,

You won't be able to convert the entities but you can protect them as placeholder tags using the embedded content processor. Try this as a catchall... think it will get most:

&\w+;

If you want to go the other way then this won't be possible at all... you'd have to write the entities themselves.  I guess you could do that with quick inserts, or maybe using autocorrect perhaps?

Regards

Paul

Hi Paul,

I deal with this issue quite often and converting entities to placeholders is really not a solution. First, we need to convert the source entities to their proper characters so the translator can understand the source text if it contains accented letters and then if the target text contains accented letters as well, we need to convert those to their respective entities as well, which so far we have to do manually.

For example:

translating the word Spain from Spanish to Czech

With accented characters: España -> Španělsko

With HTML entities: España -> Španělsko

There are different entities in source and target so converting "ñ" into a tag to transfer it safely into Czech wouldn't make much sense.

It does make sense when dealing with non-breaking spaces, symbols and other characters which don't change during translation, though.

Could there be some improvement regarding this in some new versions of Trados?

Thanks,

Vojtech

You can handle that very easily - export the Excel content to XML and then use "XML with embedded content" file type and deal with everything (incl. entities conversion) in the embedded HTML processor.

Exporting to XML can be easily done e.g. using this simple method: http://www.excel-easy.com/examples/xml.html

Of course, a definitive solution is to teach the customer that entities are TOTALLY obsolete in 21st century and today's Unicode world!