Here is the list of the language codes used in popular translation tools such as Trados, Globalsight, Passolo, OmegaT and more:
How many times has a word count being questioned? Well, it is not just a matter of what parser and settings have been used, but also the amount of considerations and exceptions in place. Here, these guys tried to explained it and they did a very good job while at it:
Matthew Guyan, in the Articulate community, wrote this great piece on 3 different ways to add subtitles (closed captions) in Articulate Stroyline:
From a localization point of view, the best and “correct” way would be the “Use Variable” method. For clients, most of the time, it is imperative to sync the text to the action. For the localization process, exporting and re-importing this text is a must for an easier cheap translation.
As a side note, just keep your lines short at creation, so you don’t have to divide in more chunks your subtitles.
Here is the list of some notable CAT tools out there: http://en.wikipedia.org/wiki/Computer-assisted_translation#Some_notable_CAT_tools
Find below the ones that run native in OS X (some might require Java), not online or via a virtual machine:
Open Language Tools
- 500 EURO (Studio Version)
- 200 EURO
Heartsome (TMX Editor)
So, how and where is that option to perform inconsistency translation checks in Passolo 2011?
Open your package/project and go to String
Click on Check… and click on Options…
You will need to select one or both of these options depending on your needs:
Inconsistent translation: There is a pre-translation available for the source string, but this does not correspond with the translation used.
Inconsistent translation within project: The same logic as above applies, but it is not only VS the available TM, but also a cross check within files.