Consistently use i18n on both the client and server side

http://confluence.sakaiproject.org/display/I18N/Best+Practices+for+Internationalized+Tools+in+Sakai

In Sakai, you can instantiate a ResourceLoader object, using the default constructor and then query it for the user's locale. That allows server-side code to honor (in this order) the user's preferred locale settings, a server default setting, and sakai's defaults (English). It may be that locale can be set at other levels also (e.g. for a foreign-language class site). It looks like java's generic ResourceBundle, which is used in the server-side code in GB2) does not honor the sakai preferences and/or settings. And the browser-side code, while attempting to respect the user's local preferences would not have any info about the sakai preferences. This could lead to great inconsistencies in strings that are localized on the server vs strings localized on the browser.