DC++ changing the internationalization capabilities
January 23, 2008 2 Comments
The next version of DC++ will feature a change in its structure for internationalization (i18n).
This all is possible thanks to gettext, which is a tool for allowing applications i18n in a very standardized manner, and is available on a multitude of platforms.
Before, all visible strings in DC++ had to be written and stored in a specific manner, where we used XML files to use the texts. This could be annoying, as you needed to constantly check what a string was called when you wanted to use it.
In the next version all text are going to be written directly as the code is lined up. This does not change the fact that DC++ will still support i18n. However, all of the XML files are going to render useless, as DC++ will drop its support for it.
The new format is .pot or .po, and our Launchpad translation site will allow you to translate strings in a much faster way; Strings that also exist in other applications are crosslinked to the DC++ project as suggestions, so for some stuff you don’t even need to input anything. It’s just to click on a particular field.
There’s as of yet no tool to convert the XML files to .pot (or .po) files. So if anyone’s up to some work, we’ll publish your tool, allowing people to do the conversion.