|
|
| (14 intermediate revisions by 8 users not shown) |
| Line 5: |
Line 5: |
| name=Building KDE's l10n Module| | | name=Building KDE's l10n Module| |
|
| |
|
| pre=[[Getting_Started/Sources/Using_Subversion_with_KDE|Using Subversion with KDE]]<br>[[Getting_Started/Build/KDE4|Building KDE From Subversion]]<br>[[../i18n|Writing Applications With Localization in Mind]]| | | pre=[[Getting_Started/Sources/Using_Subversion_with_KDE|Using Subversion with KDE]]<br>[[Getting_Started/Build|Building KDE From Subversion]]<br>[[../i18n|Writing Applications With Localization in Mind]]| |
|
| |
|
| }} | | }} |
|
| |
|
| == Abstract ==
| |
|
| |
|
| For those working on applications in KDE's main repository, building and installing language support from KDE's localization (l10n) module is a good idea. Doing so will allow you to test applications in other languages so as to spot problems related to localization that may exist in KDE. Learn how to do just that in this tutorial.
| | This page was outdated, please see https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source and https://api.kde.org/frameworks/ki18n/html/index.html |
| | |
| == Step 1: kdesdk ==
| |
| | |
| First, checkout the <tt>kdesdk</tt> module from the repository, then build and install it. If you have trouble building the kdesdk module, you can skip the troublesome parts. The main thing you need from the kdesdk module is the poxml folder. KBabel is also nice to have but not essential.
| |
| | |
| == Step 2: l10n ==
| |
| | |
| You must download, build and install each language in the l10n module separately. You can check out and build just the German, and XX languages using the following procedure:
| |
| | |
| svn co -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4 l10n
| |
| cd l10n
| |
| svn up scripts
| |
| svn up templates
| |
| svn up x-test
| |
| svn up de
| |
| ./x-test/internal/update_xx.sh
| |
| ./scripts/autogen.sh de
| |
| ./scripts/autogen.sh x-test
| |
| | |
| Once this is done, switch to your build directory, start cmake in the <tt>l10n/x-test</tt>, <tt>l10n/de</tt>, etc directories that you wish to build the language support for one at a time. You may then make and install from the build directory.
| |
| | |
| {{tip|Do not combine make and make install in a single step. It won't install anything.}}
| |
| | |
| The {{path|./x-test/internal/update_xx.sh}} step uses the transxx program in kdesdk/poxml to automatically produce the XX language translation. If you were not able to build the kdesdk/poxml files, skip the {{path|./x-test/internal/update_xx.sh}} step. You'll have to rely on someone else running it and committing to the code repository.
| |
| | |
| == Step 3: Test An Application ==
| |
| | |
| To run your application using, for instance, the German catalogs open a terminal (e.g. konsole) and type:
| |
| | |
| KDE_LANG=de myapp
| |
| | |
| where "myapp" is the name of the application you wish to test. Replace the "de" with the language code you wish to test, e.g. "x-test".
| |
| | |
| The German language is a good choice for testing the layout of your application, as German translated strings tend to be quite long. French is also a good choice. The x-test language is useful for identifying strings in your application that are not translated.
| |
