documentation
.HELP!
LANSA Multilingual Application Documentation
2 Setting Up LANSA to Run Multilingual Applications
LANSA Multilingual Application
previous page
next page
2. Setting Up LANSA to Run Multilingual Applications
2.1 Creating or Modifying a Partition
2.2 Specifying a Partition's Multilingual Attributes
2.3 System Message File Handling
2.4 Considerations for Exporting/Importing Multilingual Applications
previous page
start
next page
Menu
Homepage
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.3.1 LANSA-Issued Messages
2.3.2 MLTnnnn messages
2.3.3 User Message Files
2.3.4 User Message File Process Example
2.4 Considerations for Exporting/Importing Multilingual Applications
3. Multilingual Variables
3.1 Defining Multilingual Variables
3.2 Where Can Multilingual Variables Be Used?
3.2.1 Data Dictionary
3.2.2 File Definition
3.2.3 RDML and RDMLX Programming
3.3 Standard System Variables useful for Multilingual Development
4. The Repository and Multilingual Applications
4.1 Specify a Field's Multilingual Attributes
4.2 Specify a File's Multilingual Attributes
4.3 Multilingual Help Text
4.4 Multilingual Validation Rules and Error Messages
4.5 Multilingual Database Design Considerations
4.6 Multilingual Field Design Considerations
5. Creating Multilingual Applications using Functions
5.1 Specifying a Process or Function's Multilingual Attributes
5.2 Specifying Special Entries on a Process Menu
5.3 Specifying Process Parameters
5.4 Specifying process Action Bars
5.5 Multilingual Process or Function Design Considerations
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
6.10.1 Does LANSA know the correct CCSID to use for Multilingual text?
6.10.2 Changing F60CHR defaults
6.10.3 Non-multilingual Issues
6.10.4 LANSA Backward Compatibility
6.10.5 Orphan Language Record Handling
6.10.6 Help Text
6.10.7 Literals in RDML
7. Special Facilities
7.1 Multilingual Built-In Functions
7.2 The SREV Field Attribute
7.3 The $$RIGHT Help Text Keyword
Get in touch
Submit feedback about this site to:
[email protected]