|
|
|
|
|
Four ways to realize savings in localization projects
Communicate: Establish direct lines of communication between lead developer and lead localizer before project start - this can save up to 25% in overhead cost.
Automate: Apply the appropriate localization tool and workflow automation kits, formats etc. Avoid handing strings over outside of their context, a frequent mistake that leads to multiplying work steps and costs.
Validate: Choose a specific tool (e.g. Passolo, MultiLizer) over generic CAT tools (z.B. Trados, Transit), allowing for work in the actual environment and validation functions (double mnemonics, sizing issues, etc.). This minimizes misunderstandings and additional costs.
Freeze: Using "frozen software" is more economical than working with constant updates. Start documentation and help work only once the software is ready.
Three common errors to avoid in localization projects
Do I18N: Test the internationalization readiness of the software (aka I18N). Most developers just assume that their product can be localized, but often the details are huge obstacles: - Does a database sort languages such as Chinese and Russian? - How about hard codes? - Is right to left writing permitted? - Are accents tolerated in all data fields?
Don't Excel: Localization in binary, resource or script formats are possible and the code is protected. Exporting in Excel leads to a lack of contextual understanding for the translator, to errors and multiple revisions. And the distributors get angry.
Team up: Make sure translators, engineers, revisors, project managers and terminology experts work as a team. This requires experience, automation and lean project management - picking the right team becomes therefore the key to success.
| |
|
|