Internationalization 3.0

Beth KirschnerUniversity of Michigan

Sakai Internationalization

June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.2

3 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Sakai 2.7: The Good

• Strong Community Visibility• I18N focus within Maint Team (thx David!)• User interface localized (~95%)• Dynamic language/locale preferences• Dynamic time zone preferences• Continuous improvement (email templates,

localized permission labels, patches, …)• 17 Translations available (including Arabic)• 71 I18N Jira tickets closed in 2.7• QA Servers in 7 different countries

3

4 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Sakai 2.7: The Bad

• 40 Outstanding Internationalization Bugs• 27 Outstanding Feature Requests & Tasks

4

5 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Sakai 2.7: The Ugly

• No localized date & time input widget• Numeric fields not localized• Person names not localizable• Duplicate properties across many tools• No language/locale preferences per site• No centralized translation server

• Overall grade: B

5

6 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Sakai 3.0: The Good

• Localized Person Object definition• Encapsulation of user text in the user

interface (not in the kernel)• Widget (HTML) text partially localized• Chinese translation underway• Global properties support (in addition to

widget-specific)• Language/locale preferences per site

6

7 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Sakai 3.0: The Bad

• Poor community visibility• No user language/locale preferences• No timezone preferences• No localized dates, times, numbers, …• No support for mixing static/dynamic

content (e.g. java.text.MessageFormat)• Static (english) text in javascript widgets• Right-to-left language support unclear

7

8 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Sakai 3.0: The Ugly

• Need to coordinate locale preferences between Sakai 2 & Sakai 3 (hybrid installations)• Need to provide translations for both Sakai

2 and Sakai 3 (hybrid installations)• No centralized translation server

• overall grade: D-

8

9 June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Widget Localization

• (1) Supported locales must be defined in /dev/_configuration/languages.json

9

10

June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Widget Localization

• (2) Supported locales must be defined in widgets.js (for each individual widget):

10

11

June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Widget Localization

• (3) Each widget needs a bundles directory with default.json and other locales defined:

11

12

June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Widget Localization• (4) Localized properties encoded within HTML using a

"__MSG__" prefix and "__" suffix (Google gadget convention):

12

13

June 15-17 2010 Sakai Conference - Denver, CO, U.S.A.

Discussion…

• Visibility challenges: how to increase awareness of internationalization?• Technical challenges: how to resolve

outstanding issues?• Translation challenges: how to facilitate

easier translation process? • Resource challenges: who can resolve

outstanding issues?

13