Project

General

Profile

Feature #1486

UI language translation/localization

Added by xrdvx about 15 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
User experience
Target version:
-
Start date:
2009-03-28
% Done:

10%

Tags:
UI, i18n

Description

Translating the fron't end and maybe in-game language would expand you comunity, and also help already users to understand better the program.

I, personaly, would like to see it on spanish, starting to my friend accept it a little bit more. And also to allow me to understand better for what are the options, instead of being experiencing on for what is this or that.

I'm not saying "Hey, implement it for next release!" but, you can implement it when you have time, and, even better, you can only have to edit the code, because the comunity can translate it for you (if there are/is people that knows the languages).

Nothing else.

Labels: User Interface

History

#1 Updated by danij about 15 years ago

It should be relatively straight forward to implement but I suggest we wait until DED reader 2.0 where we could leverage the namespacing features with the Text definitions (I presume support for at least one unicode encoding method is part of the plan).

We also need to reconsider whether we should be doing things like the text help strings for console commands et al (cphelp.txt) via DED.

Another consideration is that of DeHackEd Text patches. As there is no inherent mechanism for support of language translation we should allow the user to determine if Text patches should be used (ideally, we could categorize text strings replaceable via deh patches and present fine grained controls over which categories of text strings are replaceable) .

#2 Updated by skyjake over 10 years ago

  • Tags set to i18n, UI
  • Status changed from New to In Progress
  • % Done changed from 0 to 10

Thanks to Qt's built-in mechanisms for this, the new UI framework is already going towards this direction. However, there is currently a problem with Qt's lupdate not understanding our PIMPL macros (strings inside private instance classes not recognized as belonging anywhere).

#3 Updated by skyjake over 10 years ago

  • Category set to User experience

#4 Updated by skyjake almost 8 years ago

  • Status changed from In Progress to Progressed

#5 Updated by skyjake over 4 years ago

  • Status changed from Progressed to Rejected

Also available in: Atom PDF