[#JM-840] Improve i18n in plugin admin console pages

Openfire

Improve i18n in plugin admin console pages

Created: 09/19/06 01:16 PM Updated: 01/23/08 07:57 PM

Component/s:

Admin Console

Affects Version/s:

3.1.0 Beta 2

Fix Version/s:

3.5.0

Time Tracking:

Not Specified

Support Plan Customer Issue:	No
Resolution Date:	01/23/08 07:57 PM
Acceptance Test - Add?:	No

Description

« Hide

i18n lookups in plugin JSP pages should be cascading – check for the key in the plugin i18n file and then if that fails, look for it in the Wildfire bundle. This is required since certain strings are used in the decorator of each page such as login.title. The current workaround is to copy those strings into the plugin i18n file.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Daniel Henninger - 01/21/08 05:29 PM

Committed a partial fix that eliminates the need for plugins to have things like login.title in their own resource configs. However, it does not solve the issue of plugins that want to reuse global strings in their own pages.

[ Permlink | « Hide ]

Daniel Henninger - 01/23/08 07:57 PM

I'm generally of a feeling that yes it's nice to reuse strings from openfire itself, but I think it's actually better for plugins to set all of their own strings, just in case Openfire needs to make some adjustments. That said, we have implemented the necessary functionality to make it so plugins don't have to have login.title and other things that are part of the mesh that don't belong to the plugin itself, so I think that will take care of the real issue. =) If you disagree, let me know!