search

mannyzhou5 / evolutionchamber

Automatically exported from code.google.com/p/evolutionchamber
0 stars 0 forks source link

UI localization #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Strings need to be externalized into resource bundles and an i18n framework has 
to be added to convert the output into various languages.

The grunt work has been done for the i18n classes and translation for 
Traditional Chinese (zh_TW).

Original issue reported on code.google.com by littlew...@gmail.com on 27 Oct 2010 at 10:29

GoogleCodeExporter commented 9 years ago

Original comment by azzur...@gmail.com on 27 Oct 2010 at 11:38

GoogleCodeExporter commented 9 years ago 
The code in the EAction classes uses getSimpleName to return the strings to 
show in the simple/detailed build order panels. This is difficult to localize 
without overriding the inherited method in all the child classes.

Original comment by littlew...@gmail.com on 29 Oct 2010 at 3:29

GoogleCodeExporter commented 9 years ago 
In Issue 103, I did just this, but only for the GUI part of the application.  
There are tons of hard-coded strings throughout the rest of the application.  
I'd be willing to do the grunt work if you think that this issue is important.  
And I don't think you'd really be able to localize the parts that use the 
actual names of the classes.

Original comment by mike.angstadt on 3 Nov 2010 at 1:53

GoogleCodeExporter commented 9 years ago

Original comment by Frit...@gmail.com on 6 Nov 2010 at 1:13

GoogleCodeExporter commented 9 years ago 
littlewild: Did you mean to say that you can provide a Traditional Chinese 
translation?  If so, that would be great! :)  i18n work has been finished 
(Issue 103), so all that needs to be done is to translate the .properties file. 
 The file is located in the "com.fray.evo.ui.swingx" package.

Merging this issue this Issue 103.

Original comment by mike.angstadt on 10 Nov 2010 at 5:44