HTML encoding foreign language characters

Dear community,

We are currently handling HTML files (exports from MadCap Lingo) for one of our clients.

After translation, the HTML encoding of special and foreign language characters ends up in the target file. For example "ä" for "ä". What is the correct setting to use  in order for the character itself and not the encoding to appear in the target? 

Thank you in advance for your help!

Anthoinette

Parents
  • You need to make some play with the entity converting in the corresponding file type in your project. From what I remember we have achieved the best results, when entity conversion was completely switched off. But as this can be really an individual setting, please check yourself.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • Fully agree, HTML entities are history for quite some time... every "normal" application nowadays understands UTF-8 perfectly.
    Most of these encoding/entities problems are caused by lame users/clients using lame applications with lame default settings (because they were created by lame US-based programmers who have no idea that there are also other languages on this planet than English), etc.

    So, using simple rule - use UTF-8 with BOM during the entire file/project lifecycle (unless there is a really serious reason to not to) - guarantees flawless process... including Trados Studio not converting character to/from entities, etc.
Reply
  • Fully agree, HTML entities are history for quite some time... every "normal" application nowadays understands UTF-8 perfectly.
    Most of these encoding/entities problems are caused by lame users/clients using lame applications with lame default settings (because they were created by lame US-based programmers who have no idea that there are also other languages on this planet than English), etc.

    So, using simple rule - use UTF-8 with BOM during the entire file/project lifecycle (unless there is a really serious reason to not to) - guarantees flawless process... including Trados Studio not converting character to/from entities, etc.
Children