Better Internationalization
Status: Beta
Brought to you by:
avivey
Menu
▾
▴
#8 Better Internationalization
Int'ltion is now based on a set of public static string arrays. That means different languages must be either compiled separately, or else some reflection/class-loader magic needs to be applied for this.
Also, this string file is often accessed from less-natural places (presumably due to the way enums are implemented in C#).
Task: find the best possible solution for internationalization, while keeping everything perfectly OO; OR, prove that can't be done, and find a decent solution.
Hint: you're not the first to come by this problem. consult uncle Google.
Discussion
Anonymous
... it's been a while since I looked at the code. I know, I suck at timeliness.
Funny thing is, I actually have figured out how to handle I18N; I just may not have really pushed my work upstream. Anyone besides me still interested in this game? I see a few variants have sprung up on Android and other mobile device app stores in the time since I last checked. I have planned to start again, sometime soon -- like the Phoenix, rising from the ashes...
I continued to develop the project on the site: https://github.com/LeonisX/space-trader
I plan to conduct deep code refactoring as well as use internalization.
Internalization can be implemented in several ways, I will do this through reflection.