Comprehensive Language Translation Hub

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
    * 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.

Translations Page

You can specify the desired build languages in the Languages Tab page.

The information presented in this article can be applied in a similar fashion toTranslations Page from Visual Studio Extension Project , Updates Configuration Project , Modification Package Project and Merge Module Project .

You can manage, create and register translation dictionaries for your project in theDictionaries Tab page.

Translate project strings, specify project segments for translation and generate dictionaries for untranslated project strings from the Project Strings Tab .

Change or update default strings translation, save and manage dictionaries in the repository from the Default Strings Tab .

Testing the installation User Interface

Use the [Test Installation UI ] toolbar button in the “Translations” page. This will create a temporary package in the Temp folder and run it without performing an actual installation. Since the package is not installed on your machine, only the installation UI sequence can be tested.

This option requires at least an Enterprise or Architect project type.

Testing the maintenance User Interface

Use the [Test Maintenance UI ] toolbar button in the “Translations” page. This will create a temporary package in the Temp folder and run it without performing an actual installation. Your product is temporarily registered with Windows Installer so the maintenance UI sequence can be tested..

This option requires at least an Enterprise or Architect project type.

Topics

• Languages Tab
  Building your MSI package in several languages.
• Dictionaries Tab
  Using and creating translation dictionaries to translate MSI packages in other languages.
• Project Strings Tab
  Translate project strings and save them to a custom dictionary.
• Default Strings Tab
  Translate default strings from the dictionary.

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: