| Prev | Chapter�10.�Kernel Documentation | Next |
|---|
- by Henry Minsky, +
This document describes the requirements for functionality in the OpenACS platform to support globalization of the core and optional modules. The goal is to make it possible to support delivery of @@ -45,7 +43,7 @@ kind of globalization support would be large and ongoing, since without a mechanism to incorporate the locale-specific changes cleanly back into the code base, it would require making a new fork -of the source code for each locale.
A globalized application will perform some or all of the +of the source code for each locale.
A globalized application will perform some or all of the following steps to handle a page request for a specific locale:
Decide what the target locale is for an incoming page request
Decide which character set encoding the output should be @@ -79,8 +77,8 @@ developer.
What do they need to modify to make this work? Can their localization work be easily folded in to future releases of OpenACS?
A developer needs to author a web site which operates in -multiple languages simultaneously. For example, arsDigita.com with -content and navigation in English, German, and Japanese.
The site would have an end-user visible UI to support these +multiple languages simultaneously. For example, www.un.org with +content and navigation in multiple languages.
The site would have an end-user visible UI to support these languages, and the content management system must allow articles to be posted in these languages. In some cases it may be necessary to make the modules' admin UI's operate in more than one @@ -113,7 +111,7 @@ the system. A locale refers to a language and territory, and is uniquely identified by a combination of ISO language and ISO country abbreviations.
See -Content +Content Repository Requirement 100.20
10.10 Provide a consistent representation and API for creating and referencing a locale
10.20 There will be a Tcl library of locale-aware formatting and parsing functions for numbers, dates @@ -131,13 +129,13 @@ computed by the following method, in descending order of priority:
get locale associated with subsite or package id
get locale from user preference
get locale from site wide default
20.20 An API will be provided for getting the current request locale from the -ad_conn structure.
30.0
A mechanism must be provided for a developer to group a set of arbitrary content resources together, keyed by a unique identifier and a locale.
For example, what approaches could be used to implement a localizable nav-bar mechanism for a site? A navigation bar might be made up of a set of text strings and graphics, where the graphics themselves are locale-specific, such as images of English or -Japanese text (as on www.arsdigita.com). It should be easy to +Japanese text (as on www.un.org). It should be easy to specify alternate configurations of text and graphics to lay out the page for different locales.
Design note: Alternative mechanisms to implement this functionality might include using templates, Java ResourceBundles,