Details
-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution:
Out of Date
-
Affects Version/s: None
-
Fix Version/s: 3.2.3.Final
-
Component/s: z - Legacy - integration
-
Labels:
Description
This feature request is for the overall localization of JBoss Tools. To start with, we need at least the following locales/languages:
- Japanese (ja_JA)
- Simplified Chinese (zh_CN)
- Brazilian Portuguese (pt_BR)
- Spanish (es_ES)
- French (fr_FR)
- German (de_DE)
We can add sub-tasks and/or dependencies as appropriate.
Gliffy Diagrams
Issue Links
- is blocked by
-
JBIDE-3557
Externalise English strings (move them from source code into .properties)
-
- Closed
-
-
JBIDE-3970
Japanese translation of JBossTools properties
-
- Resolved
-
- is incorporated by
-
JBDS-695
Translation of JBoss Developer Studio (L10n)
-
- Resolved
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Bulk move to CR1
Denis Golovin
added a comment - Bulk move to CR1 Prakash, you got this at the last triage discussion. Please let us know the importance of these according to demand.
Max Rydahl Andersen
added a comment - Prakash, you got this at the last triage discussion. Please let us know the importance of these according to demand. The list of languages given in the original description are the right ones to be tackled. Most of the demand is for Simplified Chinese and Japanese. We should tackle those 2 languages to start with at the minimum.
I recommend we complete these localization for those 2 languages for JBDS 3.0.
As a last resort, we need to make sure the I18N is complete so that L10N can be done after the release by local teams if needed.
prakash aradhya
added a comment - The list of languages given in the original description are the right ones to be tackled. Most of the demand is for Simplified Chinese and Japanese. We should tackle those 2 languages to start with at the minimum.
I recommend we complete these localization for those 2 languages for JBDS 3.0.
As a last resort, we need to make sure the I18N is complete so that L10N can be done after the release by local teams if needed.
No resources allocated for this.
Max Rydahl Andersen
added a comment - No resources allocated for this. This issue has gone untended since 2011 with no resources allocated, so I'm closing it as Out of Date. If you disagree, please open a new issue re: translations / langpacks / Babel. Also please provide some resources. 
Nick Boldt
added a comment - This issue has gone untended since 2011 with no resources allocated, so I'm closing it as Out of Date. If you disagree, please open a new issue re: translations / langpacks / Babel. Also please provide some resources. 
As a point of comparison, this is the current top 10 list for Babel coverage in Galileo:
Babel - Translation statistics
project_id version name locale pct_complete
eclipse 3.5 Chinese Simplified 94.52
eclipse 3.5 French 93.94
eclipse 3.5 German 93.66
eclipse 3.5 Japanese 93.32
eclipse 3.5 Korean 92.73
eclipse 3.5 Chinese Traditional 92.45
eclipse 3.5 Spanish 89.22
eclipse 3.5 Portuguese Brazilian 79.63
eclipse 3.5 Portuguese 79.22
eclipse 3.5 Italian 77.01
http://babel.eclipse.org/babel/stats.php?project_version=eclipse|3.5
Korean and Chinese (Traditional) appear to be popular with Eclipse users (or at least Eclipse translators).