Language translations

From SQLiteStudio
Revision as of 21:54, 20 July 2016 by Googie (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Would you like to contribute to SQLiteStudio translations?

Message files and tools for translating


Files containing messages to translate are XML files. You can open them with either plain text editor (using UTF-8 encoding), or you can use linguist, a Qt tool application for translator, which assists with translating and makes it really handy. I really recommend using linguist, it speeds up translating.

Download links for only a Qt linguist (pick one):

  • For Windows and MacOS X this is recommended:
    • The most recent version is always included with the whole Qt (click here to download). It can be a little heavy, because all Qt libraries will also be installed, but you get the best linguist version there is. Unfortunately other download pages have usually a bit outdated linguist. Install only one Qt version, only for Destkop, like at the picture below (otherwise you will end up with many versions taking insane amount of your disk space and will take long to download):
Qt installation for translators.png
  • For Linux:
    • you probably have linguist in your distribution repository, just install it, if you don't have it already. It may be included in the general "qt" package, or in separate "linguist", or "qt-linguist", or whatever your distribution names it.
  • For Windows:
  • For MacOS X:

Linguist manual:


You will also need a Subversion client (for Linux and MacOS X it's the "svn" command line application, for Windows there's the TortoiseSVN).


  1. You need to ask SQLiteStudio team for access to SQLiteStudio subversion repository (see contact page or ask on forum). In response you will be provided with login and password.
  2. "Checkout" the translations project from subversion URL: svn://
    • For Linux and MacOS X it would be:
      svn co svn:// local_directory_for_translations
    • For Windows just right click in the new, empty folder and select "Checkout" from TortoiseSVN menu, then paste the SVN URL from above to the URL input.
  3. Once the translation files are downloaded, you can run Linguist and start translating.
  4. When you're finished, you need to commit changes.
    • For Linux/MacOS X go to directory with translations and execute:
      svn ci -m "Next part of translation for My Language."
      If you don't know what to write as description, leave it empty.
    • For Windows right-click on the translations directory, select "Commit" and provide brief description of what you've done. If not sure what to write, just leave it empty.
  5. Next time you will want to translate, just start by updating translation files from repository. This way you will know you're translating the most recent message files (and they change from time to time, because new messages are added, or existing are changed, etc).
    • Under Linux/MacOS X go to directory with translations and execute:
      svn up
    • Under Windows right-click on translations directory and select "Update" from TortoiseSVN menu.

Remember to update files before starting translation, otherwise you will run into conflicts when commiting the files.

I ran into SVN conflict. Now what?

Best way to deal with it is to copy files you just translated to some other directory. Then tell subversion to use files from the repository (this will delete your changes from those files, that's why you have to back them up first).

  • Under Linux/MacOS X:
    svn resolve --accept theirs-full path/to/my/translation_XX.ts
  • Under Windows right-click on the repository, select "Resolve conflicts" and from the dialog pick "theirs" as the method of resolving.

Afterwards use some sort of comparing utility (like "compare files" in Total Commander, or in Krusader), or anything like that. You need to manually find out what are the differences and merge them correctly.

I'm sorry it hurts, but I told you - update files before translating them. Learn your lesson.

Testing your translation

If you want to see how your translations look, even before they are compiled into the application, you can do it as follows:

  1. Pick "Release" from Linguist File menu - it will create a *.qm file - you have to do it against all files you want to test,
  2. Create a folder named "translations" or "msg" in your SQLiteStudio directory (next to the executable you usually run)
  3. Put *.qm files (output from the Release operation) into the created directory,
  4. Run SQLiteStudio,
  5. You should be able to pick your new language in "Configuration" dialog, on "Look & Feel" tab,
  6. Confirm Configuration dialog and restart the application.
Info.pngIf you're testing updated translations (you have only added/updated translation messages in an existing translation), you can test them in the same way as above, just skip steps 5 and 6). Translations placed in "translations" or "msg" directory have higher precedence, than translations compiled into the application's binary.

Current status

See language translations


Any questions related to translations can be asked on SQLiteStudio translations forum or directly through e-mail specified at contact page.