LANSA Multilingual Application Guide
Table of contents
-
Multilingual Application Design
- About this Guide
-
1. Introduction
- 1.1 What is Multilingual Support?
- 1.2 When is it necessary to use Multilingual Support?
- 1.3 The Developer's Environment and the End User's Environment
- 1.4 The Difference Between National Language and Multilingual Support
- 1.5 Major Language Groups
- 1.6 Internationalization with Unicode
- 1.7 Restrictions and Limitations
-
2. Setting Up LANSA to Run Multilingual Applications
- 2.1 Creating or Modifying a Partition
-
2.2 Specifying a Partition's Multilingual Attributes
- 2.2.1 Language Code
- 2.2.2 Language Description
- 2.2.3 Partition Description
- 2.2.4 IBM i EBCDIC CCSID
- 2.2.5 Windows ANSI code page
- 2.2.6 ISO language code
- 2.2.7 Default Language
- 2.2.8 Development Language
- 2.2.9 DBCS support required
- 2.2.10 RLTB support required
- 2.2.11 Locale uppercasing required
- 2.2.12 IGC required
- 2.2.13 IGC Function Key
- 2.2.14 IGC Description
- 2.2.15 IGC Line Number
- 2.2.16 User Message Files
- 2.2.17 Menu Options
- 2.2.18 Function Keys
- 2.3 System Message File Handling
- 2.4 Considerations for Exporting/Importing Multilingual Applications
- 3. Multilingual Variables
- 4. The Repository and Multilingual Applications
- 5. Creating Multilingual Applications using Functions
-
6. Tips and Techniques
- 6.1 Use a "Scaling" or "Test Card" Language
- 6.2 Aligning Column Headings in Multiple Languages
- 6.3 Development of Extended Naming Standards
- 6.4 Use the Design View Language
- 6.5 If the Wrong Language (or No Language) Appears
- 6.6 Multilingual Action Bars
- 6.7 Translation Tables Used by Host Monitor and Export to PC
- 6.8 Supporting International Date Formats
- 6.9 Microsoft Windows Multilingual Operating Environment Guidelines
- 6.10 Multilingual Text Handling
- 7. Special Facilities