|
Is it only a question of jsp/vm translation or source codes too? What I mean is whether it can be translated using deployed stuff or it requires `special access' (ie. developer license and access to source code).
Mixing transaltions is bad idea in our firm. We have a bit different vocabulary for things used in JIRA ie. JIRA's "project" is our "product" because project is registered/managed labor which changes state of our "product" from one version to another... mixing project and product is in that way misleading. Hi,
To fully internationalise the Administration Interface access to JIRA's source wouldbe required, mainly for internatinalising error messages as they are generated in code. I am sure there will be other places where "strigs" are hardcoded in the source code, but there should not be too many. Please note that all commercial customers receive access to full JIRA source code. So you do not need to purchase a special Developer license, jsu a regular commercial one. Thanks, |
|||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Administration panel has no internationalization
This is actually by design - we do strive to keep all of JIRA's non-administration pages fully internationalised - but the administration pages are currently only available in English. It would require quite a lot of work to fully internationalise this section.
-Keith