I'm aware that Trados automatically adapts/recognizes measurements and dates/times. http://producthelp.sdl.com/SDL%20Trados%20Studio/client_en/About_Auto-Localization.htm
However, I cannot find any information on what exactly is considered a unit of measurement and what is not.
For example, "100km" is detected as a measurement but "100km/h" is not. Is anyone aware of what is determined to be a measurement or is there a list of the units somewhere?
That's a very good question Jesse. Generally Studio takes its auto-localization criteria from the operating system of your computer. So if Microsoft knows what it is then we do, and whatever Microsoft thinks it should be we do too. This is good and bad depending on your source material. It also doesn't cover everything, so anything not covered is either added manualy by the development team or not recognised at all.
There is no list of recognised units published anywhere as far as I am aware.
I went through an exercise a little while ago where I took every measurement in the SI Units publication and ran it through Studio to see what was recognised and what was not, as well as using the incorrect forms (spacing errors) to see what we did there. This list is with the development team, but this isn't a high priority item so I can't tell you when this might be resolved.
In the meantime useful solutions are Terminjector and Regex Match AutoSuggest provider. The former gives you the leverage for pre-translation, the latter is more flexible as you work.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
That's a very good question Jesse. Generally Studio takes its auto-localization criteria from the operating system of your computer. So if Microsoft knows what it is then we do, and whatever Microsoft thinks it should be we do too. This is good and bad depending on your source material. It also doesn't cover everything, so anything not covered is either added manualy by the development team or not recognised at all.
There is no list of recognised units published anywhere as far as I am aware.
I went through an exercise a little while ago where I took every measurement in the SI Units publication and ran it through Studio to see what was recognised and what was not, as well as using the incorrect forms (spacing errors) to see what we did there. This list is with the development team, but this isn't a high priority item so I can't tell you when this might be resolved.
In the meantime useful solutions are Terminjector and Regex Match AutoSuggest provider. The former gives you the leverage for pre-translation, the latter is more flexible as you work.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
