i18n requirements and goals (draft)

i18n requirements:

  1. Any character available in UTF-8 or through UTF-8 encoding should be available for any operation. UTF-8 should be properly escaped in URLs. UTF-8 should be preserved when importing or exporting.
  2. Any user-displayed self-sufficient text should be built in a way that permits it translation without being constrained by the default language structure.
  3. The way to translate the user-displayed texts should be well documented.
  4. A way to debug live how the user-displayed text is built should be available.
  5. The display of dates, numbers and other not purely textual user-diplayed information should adapt to the locale rules of both language and country. This adaptation might be available within the framework/language used.
  6. The user-displayed information should adapt dynamically to the user preferences.
  7. The way the locale user preferences are retrieved should be consistent across an official release of sakai and well documented.

i18n goals:

  1. Dynamic editing of translations
  2. Display names for tools or other repeated UI texts should be translated once and shared across the whole Sakai release