Skip to content

Resource Strings and Localization

Resource strings are named text constants used throughout your project. By using strings instead of hardcoded text, you can create a single installer that supports multiple languages seamlessly.

Resource strings are identified by a # prefix (e.g. #BrowseFolders). At runtime, the package replaces them with the actual text for the user’s selected language.

Click the Resource Button Resource string button next to any text field to insert a string.

Manage all your project’s text and translations through the Resource String Editor, accessible via the toolbar or the Language Manager.

Resource String Editor

Double-click a string or click Edit to open its properties:

Resource String Properties

FieldDescription
IDUnique name starting with # (e.g. #UserWelcome). Custom IDs can be renamed; Global IDs cannot.
ValueThe actual text displayed to the user. For example, #UserWelcome might be “Welcome!” in English and “Bienvenue !” in French.

Multi-selection

Select multiple strings for batch Edit, Delete, or Translate operations.

Translate with AI

Automatically translate selected strings into all other project languages using your configured AI provider.

Fill Missing Strings

Copy all identifiers from the current language to other languages where they are missing — ensures all translation sets have the same structure.

Language Tools

Access import/export options and additional language management utilities.

Each language file has its own settings:

PropertyDescription
LCIDWindows Locale Identifier (e.g. 1033 for English, 1036 for French) — used for automatic detection
AuthorName of the translator
EmailContact email for the translator
Reading DirectionLTR or RTL (for Arabic, Hebrew, etc.)
  1. Add languages via the Language Manager.
  2. Use resource strings (identifiers) for all text fields in your package.
  3. Provide translations in the Resource String Editor for each language.
DetailValue
File format.pbr — UTF-8 XML
Reading directionLTR and RTL supported
Import/Export.pbr files reusable across projects