We see an upward trend in the usage of this format and applaud it for its properties. For the purposes of localization it can be treated as a software file which has some great advantages.
- Increased leverage from version to version (Understand: “quicker turnaround”, “lower cost”)
- Automated post-translation quality assurance (Understand: “less or no post-translation debugging”)
A normal XML parser will correctly separate the text from the code and make the files localizable. However, you will not be able to capitalize on the above benefits. To handle XAML files correctly, EzGlobe developed a specific parser that not only separates the text from the code but also assigns unique IDs (XAML IDs (x:Key)) to each string.
Strings translated in XAML files that were parsed as software files (using EzGlobe’s parser) are stored in the translation memory inclusive of additional metadata (unique IDs). Our translation process identifies the strings based on the “string ID” and “string source text”. It uniquely identifies each string and leverages the strings that were already translated in a previous release. These strings can be safely reused without the need for review, thus they are free of charge.
In terms of the post-translation quality assurance, our standard QA includes an automated test that detects problems with:
- Translation Inconsistency
- Inconsistent/Missing Hotkeys
- Placeholder Characters
- Control Characters
- Lead/Tail Spaces
- Overlapping Controls
- Spell Check
- Duplicate Accelerators
The translated files we deliver are free of the above errors.
Do you develop using Extensible Application Markup Language (XAML)? If you have any questions do not hesitate to contact us.