[#CONF-8269] Bundled plugins without internationalized help text.

Confluence

Bundled plugins without internationalized help text.

Created: 15/Apr/07 07:34 PM Updated: 17/Sep/07 03:51 AM

Component/s:

Internationalisation, Plugins

Affects Version/s:

2.3

Fix Version/s:

2.5

Time Tracking:

Issue & Sub-Tasks

Issue Only

Not Specified

Issue Links:

Cloners

This issue is derived from:

~~CONF-6817~~ Missing localization strings for Notation Guide

Part

This issue incorporates:

~~CONF-8275~~ Info macros help not internationalized

~~CONF-8274~~ Chart macro help not internationalized

Participants:	Agnes Ro [Atlassian], Charles Miller [old account, do not assign issues], Matt Ryall [Atlassian] and Neeraj Jhanji [Atlassian]
Since last comment:	1 year, 18 weeks, 6 days ago
Resolution Date:	31/Aug/07 12:02 AM
Labels:

Sub-Tasks:

All

Open

~~Please inform the location of these properties files~~

Closed

Agnes Ro [Atlassian]

Description

« Hide

See NotationGuideJP.pdf attached to ~~CONF-6817~~

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Charles Miller [old account, do not assign issues] added a comment - 17/Apr/07 01:05 AM

Note: Many of the highlighted sections of the notation guide are in fact parts of the Builder Theme, which is not shipped as part of Confluence. As such we can't fix those sections of the guide.

[ Permlink | « Hide ]

Agnes Ro [Atlassian] added a comment - 18/Apr/07 08:42 PM

The following plugins have been i18n:
-information
-layout
-livesearch
-dynamictasklist
-chart

a few were already i18n, however the properties were moved correctly from the ConfluenceActionSupport.properties file to each of the plugin's property files.

[ Permlink | « Hide ]

Agnes Ro [Atlassian] added a comment - 18/Apr/07 08:43 PM

For the third party plugins, you will may contact the plugin developers and ask them to create seperate properties files for the plugins and i18n their text.

[ Permlink | « Hide ]

Neeraj Jhanji [Atlassian] added a comment - 18/Apr/07 09:11 PM

Hi Agnes,

Thanks for the quick action on these. Before we resolve this issue, I have 2 comments:

1. If you move the i18n keys to the individual plugins, it makes it very difficult for us to track all the different property files that need to be localized for a given Confluence release. I think we have a few options:

(a) add them to the central ConfluenceActionSupport.properties file, or
(b) create a JAR of all the files that need to be localized (as is the case with JIRA), or
(c) provide clear instructions on the names and locations of all files that need to be localized in a new release of Confluence, including the bundled plugins.

2. While you are at this, could you please also take a look at CONF-8179 which is a very similar issue related to how to i18 the Activity plugin and we are having a problem understanding what to do.

Thanks very much for your support.

Neeraj

[ Permlink | « Hide ]

Matt Ryall [Atlassian] added a comment - 31/Aug/07 12:02 AM

Hi Neeraj,

It was decided to make the properties files for plugins separate to Confluence so that they can be upgraded independently. Otherwise we lose much of the benefit of making Confluence's architecture plugin-based. Unfortunately, this will make translation slightly harder.

We thought the best way for this to work for translators would be the following:

keep a list of plugins which you are intended to translate as part of your distribution, and a copy of the relevant i18n file from each
translate these files, and bundle them together in your language pack.

I notice Dave wrote a document on this a while ago. You can continue creating your own bundled-plugin.zip file, but it would be better to include these in the Japanese language pack. I've updated the document here to reflect this:

http://confluence.atlassian.com/display/DOC/Internationalising+Confluence+Bundled+Plugins

Please let me know if you need any more assistance with this.

Regards,
Matt