Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Improve i18n in plugin admin console pages

Description

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.

Environment

None

Activity

Show:

Daniel Henninger January 24, 2008 at 9:57 AM

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!

Daniel Henninger January 22, 2008 at 7:29 AM

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.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created September 20, 2006 at 1:16 AM
Updated January 24, 2008 at 9:57 AM
Resolved January 24, 2008 at 9:57 AM

Flag notifications