Make your PowerBuilder Applications Multilingual
PowerBuilder Localization
Expand Your PowerBuilder App’s Global Reach
In an increasingly interconnected world, adapting your PowerBuilder applications for different international markets has become essential. Beyond mere translation, localization involves adapting to the cultural, legal, and linguistic nuances of each target market.
This whitepaper explores the specific technical challenges of localizing PowerBuilder applications and presents practical strategies to overcome them effectively.
Read the Whitepaper
You will discover how to:
- Easily adapt user interfaces for different languages with specialized resizing tools.
- Ensure compatibility with non-Latin characters and complex scripts.
- Efficiently manage localizable resources in your PowerBuilder code.
- Integrate localization into your existing development workflows.
Whether you're planning international expansion or looking to enhance the experience of your current users across different regions, this guide will provide valuable insights to successfully implement your localization strategy.
Multilingual Features
Developer decides which parts / controls to translateAdd languages without rebuilding enabled applications
Supports all versions of PowerBuilder and all character sets
Prints in desired language, without resetting current language
Simple distribution: just install libraries and language database (no DBMS necessary)
Developer license: multi-project, no runtime royalties
Single source code,
single user application
Developers using Enable obtain just one source code which is compiled into just one multilingual application. Subsequent changes to the language database, including the revision of translations and the unrestricted addition of new languages, are made without altering the source code or the executable code in any way.
Simple, low profile enabling of source code
An application becomes multilingual with Enable by making minor changes to the source code, mainly within the Application Framework. These tweaks reflect the way the developer wishes to interact with the translation engine. Program legibility is retained thanks to a series of APIs designed to minimize the impact of localization on the original programs.