Work In Progress

Requirements

1. Configuration
   1. I18N must be configurable server wide
   2. I18N must be configurable per application
   3. I18N must be configurable per application per user
   4. I18N must be configurable per user
2. Pluggability (not a word, but you know what I mean, I like it, and I'm keeping it)
   1. I18N must be pluggable for tags
   2. Applications deployed to a Ringside server must be able to provide pluggable I18N
3. Platform support
   1. I18N content must be storable/retrievable to/from the database, including double byte character sets (i.e. Chinese, etc.)
   2. Applications must be able to render in the appropriate language based on browser, user, user-application, application, or server language preferences
   3. Tags must be able to render in the appropriate language based on broswer, user, user-application, application, or server language preferences
   4. System applications (like Profile, Friends, etc.) must render in appropriate languages based on multi-level language preferences
   5. Language preferences must be honored in the following order of precedence:
      1. User's application preference
      2. User's preference
      3. Browser setting
      4. Application setting
      5. Server setting

Research

I18N APIs & Packages

• Pear I18N
• http://php.net/gettext

Articles/Blogs/Blog Posts

• Internationalization and Localization with PHP
• Gettext
• Handling UTF-8 with PHP
• PHP I18N Blog