...
Internationalization BOF
| Anchor | ||||
|---|---|---|---|---|
|
On Decemberr 5th, there was an Internationalization BOF ("birds of a feather") as a followup to this talk which continued the conversation on how to make the process of internationalization more accessible. Following are the notes.
Existing (Technical) Problems
- SAK-8908 page and tool titles need to be internationalized dynamically (Raul/UPV and Tom/CRIM will post patches that represent a first pass solution patch posted)
- Role names and site types are not localized (Tom/CRIM will post a patch to SAK-732712397)
- First day of the week needs to be dependent on locale (Raul/UPV): patch posted (SAK-8459) (resolved)
- Message folders need to default to user's locale (Raul/UPV): Patch to be (patch posted) (SAK-12146)
- Date/Time widget needs to be developed for Velocity and JSF (SAK-36777000). Beth will post an email to the dev list requesting help.
- SAK-12299 and SAK-12300 describes problem of attaching unicode filenames to JSF tools. (patch posted for SAK-12299)
- Floating point numbers representation not locale specific: JIRA tbd
- CRIM has a patch that provides a locale-specific lookup for the Web Content tool, but this requires further evaluation for performance concerns (SAK-12396).
- The FCK Editor might be modified to provide the option for creating locale-specific text, using a language attribute tag (SAK 12398).
Translating needs to be easier and more accessible
Everyone agrees that the current process for translating properties files is unreasonable and unmaintainable. Suggestions include:
- Creating a common properties file to remove redundancies (SAK-12351)
- Beth will ask the sakai-dev list for suggestions on how Outstanding issue: How to resolve the problem of matching properties key/value pairs to their context? (Beth will post question to sakai-dev list asking for suggestions).
- One suggestion to assist the problem of out-of-context properties key/values is to update the ResourceLoader class with an option to log or otherwise annotate the relationship between a key/value property and it's context (SAK-1235212548).
- Suggestion: The sakaiproject.org web site should leverage a WIKI to facilitate translations by international users, with a goal of more visible outreach to the international community. (Beth to follow up on this).
- Help text will be localized in Sakai 2.5 (SAK-4256) – Tom/CRIM will send an email with details on how to use this new feature.
- CRIM has a patch that provides a locale-specific lookup for the Web Content tool, but this requires further evaluation for performance concerns (SAK-12396).
- The FCK Editor might be modified to provide the option for creating locale-specific text, using a language attribute tag (JIRA tbd).
- Suggestion: The sakaiproject.org web site should leverage a WIKI to facilitate translations by international users, with a goal of more visible outreach to the international community.
Higher level internationalization issues
...