[#JRA-6846] Add default translation sets for issue constant translations.

JIRA

Add default translation sets for issue constant translations.

Created: 31/May/05 08:48 PM Updated: 27/Nov/06 09:16 PM

Component/s:

Internationalisation

Affects Version/s:

3.2

Fix Version/s:

3.5

Time Tracking:

Not Specified

Participants:	Dylan Etkin [Atlassian] and Keith Brophy
Since last comment:	2 years, 34 weeks ago
Resolution Date:	04/Jan/06 04:22 PM
Labels:

Description

« Hide

Now that all issue constants (Issue Types, Resolutions, Priorities and Statues) can be associated with a translation set, as suggested by Arne Schirmacher, it would be useful to add default translation sets for each constant for each available locale.

Hence, for example, when users navigate to the German translation section for issue types, the default German translations for Bug, New Feature, Task and Improvement would already be listed.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dylan Etkin [Atlassian] added a comment - 04/Jan/06 04:22 PM

What we have done is to allow a default translation to be specified in the JiraWebActionSupport.properties file. If a translation is specified here then this will show up in all places where the translated values where previously displayed (issue creation, view issue, etc). These "default" translations will not populate the "translate issue type" screen. It was decided to leave that screen as a representation of what the translations which are stored in the db are. If a translation is entered through the UI then it will override the translations in the properties file. The properties that will set the defaults are commented out in the english (default) properties file since we populate these values into the database when we create a JIRA instance.