How to localize .resx files

 

Alchemy CATALYST processes  .resx files and builds optimised or unoptimised versions for all languages. The .resx parser processes  each .resx file individually and automatically creates the correct language variant on extraction. It is compliant with the RFC 1766 file naming convention which the Microsoft .NET Framework uses for translated .resx files.

It's very important to set the Target Language in a Project TTK when working with .resx files as Alchemy CATALYST uses the Target Language to generate the correct RFC 1766 localised filename for translated .resx files.
 

To Localize .NET Winforms

The Dialog Editor is used to translate, engineer and test .resx files that contain Winforms. This editor can display all standard .NET controls as well as custom or 3rd party controls. These controls can also be mapped to known .NET controls to improve the visualness of working on highly complex .resx files.

To Localize .NET Menus

The Menu Editor is used to translate, engineer and test .resx files that contain menus. Since the .resx file does not contain the hierarchical structure of a .NET menu, this editor displays the text in a flat list only.

To Localize .NET Strings

Use the String Editor to translate, engineer and test .resx files that contain Strings.

Inheritance Information

Occasionally it may not be possible to fully render a Winform Microsoft name for a .NET Dialog Panel Generic name given to dialog boxes. A Dialog Panel is an internal CATALYST object that is used to represent dialogs from multiple development platforms. (ie .NET Windows, Desktop Dialog boxes, SmartPhone Canvas Areas, ASP+ Pages, XLIFF Frames, Oracle Forms. etc.).Dialog Panel . in the Dialog Editor. This is because  .resx files do not always contain the necessary information for inherited winforms or 3rd Party controls. In these situations, Alchemy CATALYST will attempt to display as much as possible from the .resx file and allow3rd Party and inherited controls to be mapped to known .NET controls. This improves the visualness of the Dialog Editor in working with .resx files.

Extracting Localized .resx files

Localized .resx files need to have unique filenames in order to conform to the Microsoft .NET development guidelines. These filenames have unique language identifiers added to the original filename. For example, the file form1.resx should be renamed form1.fr.resx when localized into French.

Alchemy CATALYST creates these localized filenames automatically when .resx files are extracted from a Project Your project is where you manage and organize all the files that are to be localised. TTK. These filenames can now be used by Microsoft Visual Studio.NET to create a localized version of a .NET application.

Creating optimised .resx files

To create optimised .resx files, goto General Options- .NET Framework and select Extract only modified resources to satellite assemblies. Once this option is switched on, only changes to .resx files are stored in localized .resx files.