Version 6 (modified by aramacciotti, 4 years ago) (diff)

--

Localizing Eraser

Requirements

Localizing Eraser v6 require to be able to build its .NET solution. Then requirements are the same of building it. You can check them on CompilingEraser (Get the necessary dependencies)

What needs to be localized

Source files that require to be localized are:

  • Strings.xx.resx: there's one for most projects
  • <PageName>.xx.resx: there's one foreach form and custom controls
  • ShellExt.rc: there's only one in ShellExt Shell Extension C++ project

xx is the acronym of the target localization language.

How localize Strings

You'll find Strings.xx.resx files in the following projects:

  • Eraser
  • Eraser.DefaultPlugins
  • Eraser.Manager

Localizing these files it's really simple:

  • open file in VisualStudio.NET (with simple double clickover the file)
  • A form (see picture below) is showed with 3 (three) columns in the following order (column names are provided in english as a reference):
    1. Name: source language string
    2. Value: target language string (initially set to "(Untranslated)")
    3. Comment: a comment string
  • change the value in the second column with the translated string

Screen shot of Strings files localization

How localize Forms and Custom Controls

Each form has a number of controls that shows text and then that can be localized. Localization process is basically constituted by:

  • Choosing form language property as the target localization language
  • Change text of each control that shows text in the form

Follows details for each form actually included in the project.

Project Eraser

AboutForm
BasePanel
LightGroup
LogForm
MainForm
ProgressForm
SchedulerPanel
SettingsPanel
TaskDataSelectionForm
TaskPropertiesForm
UpdateForm

Project Eraser.!DefaultPlugins

CustomMethodEditorForm
CustomMethodPassEditor
SettingsForm

How localize Shell Extension

Attachments