DarkMultiPlayer Client

DarkMultiPlayer Client

38.8k Downloads

Internationalization support

oldmud0 opened this issue ยท 14 comments

commented

This is mostly for localization purposes as well as in case we want to fix spelling errors and the like.

commented

@RockyTV What still needs to be done for the i18n fork to be considered done? I'm Studying the code atm. Would it be wise to merge your fork into my own and just try to work from there?

commented

Gotta rework those 7-month-old branches..

commented

@Stokkie64 Sorry for the late reply.

Well, I don't know if I still have the i18n branch here, but I remember that months ago I tried using the method described above by @oldmud0: having a .resx file for each language we want to support, and adapt the UI code to use the translated languages.

However, I don't know if I still have that branch over here. If I do, I'll push it to my fork. It was pretty much done, it only needed adding the missing strings to the .resx files.

EDIT: I'm re-working the i18n branch.

commented

Haha cool stuff. I would have been happy to do it myself. But considering your progress I'll leave you to it. I will contribute several languages with the help of a linguist friend.

commented

@Stokkie64 You can finish it if you want to. I'm not holding back any stuff, but right now I am busy with some other stuff, and the development of the branch will be halted. I'd appreciate if you did continue the work.

commented

@RockyTV Sure I'll give it a go. Figuring out what you've done and still needs work shouldn't take too long.

commented

Instead of using the SettingsParser library, we could use C#'s built-in internationalization system. Or use the same method as KSP (I heard a rumor that they are testing i18n).

commented

Is the built-in i18n compatible with Mono?

commented

@oldmud0 It should be.

commented

@RockyTV I read a bit on System.Globalization and it seems to be very .resx-oriented, so you would have to make a resx/XML file for each language you want to support, containing every possible string in the UI. I don't know how fine you would be with using XML.

commented

+1

commented

This is definitely a good idea for i18n, reminds me of this post from majiir: http://forum.kerbalspaceprogram.com/threads/49268-The-Internationalization-Project. If we do get something generic perhaps a seperate KSP mod could be used as a platform.

EDIT: Also keep in mind something like this: https://www.youtube.com/watch?v=0j74jcxSunY

commented

Renaming this to Internationalisation support.