General localization procedure
- Make sure that Hard-Coded Strings inspection is activated. Refer to the section Recognizing Hard-Coded String Literals for details. If the inspection is activated, the appropriate tool tips for components display in the UI Designer tool window, and quick fix i18nize property<name> is displayed in the Form Workspace and UI Designer tool window.
-
Create properties files for each locale you want to provide for the GUI, and a default properties file without a postfix.
For example, for a dialog developed in English and localized to German and French, you might create the following properties files:
- Subscription.properties
- Subscription_de.properties
- Subscription_fr.properties
-
Go through the form, and select each component that contains hard-coded strings. Click the quick fix
icon, or press Alt+Enter to show the list of available intention actions,
and select i18nize property <name>, as shown on the following image:
- In the I18nize Hard Coded String Literal dialog box, extract hard-coded string literals to the specified properties files. Refer to the section Extracting Hard-Coded String Literals for details.
-
Edit the extracted strings in the resource bundle. Refer to the section
Editing Resource Bundle for details.
See samples in the section Using Resource Bundles for Components.
Suppressing i18nize hard-coded string quick fix
- Select a component that contains hard-coded text property.
- Click the quick fix icon, or press Alt+Enter to show the list of available intention actions.
- Hover the mouse cursor over the
i18nize property <name>
quick fix,
and click the right arrow icon
(or press right arrow key)
to reveal the submenu, as shown on the following image:
-
Click the option Suppress for component
or Suppress for all components. The list suppressed inspections appears in the
GUI Designer tool window:
on the main toolbar.
