Customizable Language Phrasing: The Key to Global Reach

Table of Contents

• Introduction
• Registration
• Using Advanced Installer
  • GUI
  • Working with Projects
  • Installer Project
    * Product Information
    * Resources
    * Package Definition
    * Requirements
    * User Interface
    * Themes
    * Dialogs
    * Slideshow
    * Translations
    * Languages Tab
    * Dictionaries Tab
    * Project Strings Tab
    * Localization Options Dialog
    * Localization Dialog
    * Localized Strings
    * Edit Translations Dialog
    * Default Strings Tab
    * System Changes
    * Server
    * Custom Behavior
  • Patch Project
  • Merge Module Project
  • Updates Configuration Project
  • Windows Store App Project
  • Modification Package Project
  • Optional Package Project
  • Windows Mobile CAB Projects
  • Visual Studio Extension Project
  • Software Installer Wizards - Advanced Installer
  • Visual Studio integration
  • Alternative to AdminStudio/Wise
  • Replace Wise
  • Migrating from Visual Studio Installer
  • Keyboard Shortcuts
  • Shell Integration
  • Command Line
  • Advanced Installer PowerShell Automation Interfaces
• Features and Functionality
• Tutorials
• Samples
• How-tos
• FAQs
• Windows Installer
• Deployment Technologies
• IT Pro
• MSIX
• Video Tutorials
• Advanced Installer Blog
• Table of Contents

Disclaimer: This post includes affiliate links

If you click on a link and make a purchase, I may receive a commission at no extra cost to you.

Localized Strings

A localized string can have different values depending on the language in which the project is being build.

There are two categories of localized strings:

• the strings included in the installation package’s UI, common to every MSI file
• the strings included in your project, that are particular to the current project: the name of your application, file names, registry values, properties etc.

The former are shipped with Advanced Installer for several languages. But you can easily create and add translations for other languages using the Translations page.

The latter are particular to every project and therefore must be specified by the user. Not every string has to be translated. For the ones you want to be localized a localization identifier must be attached.

If the localizable string is empty, then no translation will take place even if a valid localization identifier was defined.

The Localization Identifier

An unique identifier is attached to each translated string called the “Localization Identifier”. It is used to search the dictionaries and locate the value of the string in different languages.

To attach a localization identifier to a certain string you have two choices:

• leave it automatically generated (recommended)
• specify it yourself. This option is useful if you want to use a dictionary with custom IDs or dictionaries that you have already translated prior building the current project.

Did you find this page useful?

Please give it a rating:

Thanks!

Report a problem on this page

Information is incorrect or missing

Information is unclear or confusing

Something else

Can you tell us what’s wrong?

Send message

Also read: