Hello,
we are struggeling with some po-files due to a wrong representation of "umlaut" (üöä) in Trados.
If we open the files in a poeditor (i.e. https://localise.biz/free/poeditor ) they are displayed properly:
but in Trados they are displayed wrong:
Does someone know want kind of settings we have to change in Trados?
Thank you very much in advance
Hello, Fabio
what you are seeing is not a wrong representation but simply HTML encoding, as I am sure you know.
As far as I can see, the po file format definition does not have an embedded HTML decoder. I encounter the same issue when I use the bilingual Excel format to work with bilingual XML files.
The solution is actually very simple: Before you add the file to your Studio project, you replace the codes with the letters they represent:
Ü = Ü
ü = ü
etc.
I replace the Umlauts (Ä, ä, Ü, ü, Ö, ö) and the sharp s (ß).
Then you add the file to your project, translate and finalize it.
It might be necessary to reverse the replacement process before you can use the file normally or return it to your customer, but that is just as trivial.
I am using macros for this, which really makes it a breeze. Since I do this within Excel, I also do all these conversions there. You won't want to do that with a po file, so you could use Notepad++ which has a plugin that as far as I remember does all these conversions with one click for you:
All the best
Daniel
Hello, Fabio
what you are seeing is not a wrong representation but simply HTML encoding, as I am sure you know.
As far as I can see, the po file format definition does not have an embedded HTML decoder. I encounter the same issue when I use the bilingual Excel format to work with bilingual XML files.
The solution is actually very simple: Before you add the file to your Studio project, you replace the codes with the letters they represent:
Ü = Ü
ü = ü
etc.
I replace the Umlauts (Ä, ä, Ü, ü, Ö, ö) and the sharp s (ß).
Then you add the file to your project, translate and finalize it.
It might be necessary to reverse the replacement process before you can use the file normally or return it to your customer, but that is just as trivial.
I am using macros for this, which really makes it a breeze. Since I do this within Excel, I also do all these conversions there. You won't want to do that with a po file, so you could use Notepad++ which has a plugin that as far as I remember does all these conversions with one click for you:
All the best
Daniel
Translate
