Go AVDN
Be Localizable

If you have played with the Brief Demo Application , you should already see that metadata for different Locale s just reside in different XML files, with the Locale Meta ID inserted into the file names.

This is the core mechanism that Meta Facility used to retrieve metadata in a Locale sensitive way. With this understanding in mind, localizing metadata comes straight forward.

Normally when a program is writen, the designer or programmer should provide default metadata for all Locales, by writing XML files with empty Locale Meta ID in name.

Then a localization team could copy these XML files into new ones those with specific Locale Meta ID inserted to the file names, and further translate the file contents.

But in real world, programs may in a long period of development, mean while metadata may change increamentally. This need coordination between the programmers and translaters.

By convention, a programmer should write comments in those XML files containing metadata, to clarify if a fragment of XML content inside that file should be localized or not, and provide translation hints for any special meaning or usage of metadata.