Home

Documentation

Is not finished yet...

The expected approach for localization

The project should be localized by putting different text resources into ResX files. The following approach should be used:

• resources for the base project language are placed into SomeResources.resx file (without culture code suffix);
• resources for every additional language are placed into SomeResources.XX.resx file, where XX - culture code (e.g. de - for German, or ru - for Russian).
• the base ResX file and files for additional languages are placed in the same folder.

It is also expected that text resources which should be translated are marked with tags (e.g. [translate me]). For example, the base file SomeResources.resx has a text resource (key-value):

MainWindowTitle = Amazing application!

Then the German file SomeResources.de.resx should have the resource:

MainWindowTitle = [translate me] Amazing application!

The tag means that this is a resource taken from the base language file, and that it will be translated into German language later. The value after tag shows what text should be translated. It is convenient because this way we don't have to look up to the base file during translation.

However, the idea is that developers don't have to translate the project into different languages. They should maintain only the base resource file. The tool has a feature for synchronizing all resources and tagging everything that should be translated.

Synchronizing resource files

Exporting resources which should be translated

Importing translated resources