Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Step 10. Localize the Application

Step 10. Localize the Application

Four sets of resource bundles contain the strings that are displayed in an IDD application.
Each set includes the following components:
  • The default file.
  • A placeholder English language file. This file can be empty.
  • Localized versions of the file, if needed.
For example, for the MessageBundle set, there is the default file MessageBundle.properties, and the placeholder English language file MessageBundle_en.properties.
Each resource bundle file is a UTF-8 encoded properties file. Each entry in the file is a name/value pair,
<name>=<value>
. Examples:
title=Business Data Director locale=Locale search=Search
For each entry:
  • <name> is a fixed value that is referenced by the IDD application and cannot be changed
  • <value> is the part that can be localized
To localize the application:
  1. Use the IDD Configuration Manager to add resource bundle files to an IDD application, either by including them in the application ZIP file that is imported, or by importing them individually into an existing IDD application.

0 COMMENTS

We’d like to hear from you!