< Development | Tutorials | Localization Revision as of 18:34, 1 December 2007 (view source)Aseigo (talk | contribs) (→Step 2: l10n)← Older edit Revision as of 17:17, 1 January 2008 (view source) 188.8.131.52 (talk | contribs) (→Step 2: l10n: - language name is "x-test" not "xx". really")Newer edit → Line 27: Line 27: svn up x-test svn up x-test svn up de svn up de − ./xx/internal/update_xx.sh+ ./x-test/internal/update_xx.sh ./scripts/autogen.sh de ./scripts/autogen.sh de ./scripts/autogen.sh x-test ./scripts/autogen.sh x-test Revision as of 17:17, 1 January 2008 Building KDE's l10n Module Tutorial Series Localization Previous Using Subversion with KDEBuilding KDE From SubversionWriting Applications With Localization in Mind What's Next n/a Further Reading n/a Contents 1 Abstract 2 Step 1: kdesdk 3 Step 2: l10n 4 Step 3: Test An Application 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. Step 1: kdesdk First, checkout the kdesdk 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 l10n/x-test, l10n/de, 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 ./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 ./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. "xx". 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 XX language is useful for identifying strings in your application that are not translated. Retrieved from "https://techbase.kde.org/index.php?title=Development/Tutorials/Localization/Building_KDE%27s_l10n_Module&oldid=19045" Category: Tutorial Content is available under Creative Commons License SA 4.0 unless otherwise noted.