Difference between revisions of "Internationalization/User guide"
m (outline) |
|||
Line 6: | Line 6: | ||
We divide this task into two parts: | We divide this task into two parts: | ||
− | # Loading translated strings from a message catalog - or in our terminology, from a 'datasource' | + | # Loading translated strings from a message catalog - or in our terminology, from a 'datasource'. |
+ | One can imagine various datasources, but currently the only supported one is a file. | ||
+ | ## Formatting numbers, currency values and dates. | ||
+ | This information can be fetched directly from the operating system. | ||
− | + | ==Interface== | |
+ | |||
+ | ===Locale=== | ||
+ | |||
+ | ===Locale Manager=== | ||
+ | |||
+ | ===Locale ID === | ||
+ | |||
+ | ===Putting it all together=== | ||
+ | |||
+ | ==Datasources== | ||
+ | |||
+ | ===File=== | ||
+ | |||
+ | ====File format==== | ||
+ | |||
+ | ====File Manager==== |
Revision as of 17:15, 8 October 2006
Contents
User documentation for the i18n library
Overview
The i18n library is intended to enable localisation of Eiffel programs.
We divide this task into two parts:
- Loading translated strings from a message catalog - or in our terminology, from a 'datasource'.
One can imagine various datasources, but currently the only supported one is a file.
- Formatting numbers, currency values and dates.
This information can be fetched directly from the operating system.