(→Quality Assurance) |
m (Fix syntax highligthing.) |
||
| Line 37: | Line 37: | ||
: This little utility, once activated, can present a report about conflicting shortcuts in menus. Not only is this helpful for translators but also for developers. A little hand editing of {{path|`kde-config --localprefix`/share/config/kdeglobals}} activates this feature: | : This little utility, once activated, can present a report about conflicting shortcuts in menus. Not only is this helpful for translators but also for developers. A little hand editing of {{path|`kde-config --localprefix`/share/config/kdeglobals}} activates this feature: | ||
| − | < | + | <syntaxhighlight lang="ini"> |
[Development] | [Development] | ||
CheckAccelerators=F12 | CheckAccelerators=F12 | ||
AutoCheckAccelerators=false | AutoCheckAccelerators=false | ||
AlwaysShowCheckAccelerators=false | AlwaysShowCheckAccelerators=false | ||
| − | </ | + | </syntaxhighlight> |
: Pressing F12 will show a dialog containing which accelerators in the currently focussed interface conflict and provide suggestions for new accelerators. If no accelerators conflict or Dr. Klash has nothing to suggest, no popup dialog will be displayed. | : Pressing F12 will show a dialog containing which accelerators in the currently focussed interface conflict and provide suggestions for new accelerators. If no accelerators conflict or Dr. Klash has nothing to suggest, no popup dialog will be displayed. | ||
| Line 52: | Line 52: | ||
: After you've built l10n-kde4/x-test and installed it, run your application using the "x-test" locale. This can be done by launching it from the command line like this: | : After you've built l10n-kde4/x-test and installed it, run your application using the "x-test" locale. This can be done by launching it from the command line like this: | ||
| − | + | <pre> | |
| − | + | > KDE_LANG=x-test kspread | |
| − | + | </pre> | |
: This will start KSpread using the "x-test" locale no matter what your current language setting is. Look for strings that do not have the xx's. If xx's are missing from a string, it could be due to missing i18n calls or even missing or incorrectly generated .pot files. Consult the i18n tutorials for further information. | : This will start KSpread using the "x-test" locale no matter what your current language setting is. Look for strings that do not have the xx's. If xx's are missing from a string, it could be due to missing i18n calls or even missing or incorrectly generated .pot files. Consult the i18n tutorials for further information. | ||
| Line 63: | Line 63: | ||
You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of {{path|l10n/de/messages/kdebase/konqueror.po}}: | You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of {{path|l10n/de/messages/kdebase/konqueror.po}}: | ||
| − | + | <pre> | |
| − | + | #: konq_mainwindow.cc:3707 konq_tabs.cc:84 | |
| − | + | msgid "&New Tab" | |
| + | msgstr "Neues &Unterfenster" | ||
| + | </pre> | ||
The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from {{path|konq_mainwindow.cc}} and also from {{path|konq_tabs.cc}}. This saves the translators from having to translate the same identical string twice. | The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from {{path|konq_mainwindow.cc}} and also from {{path|konq_tabs.cc}}. This saves the translators from having to translate the same identical string twice. | ||
| Line 75: | Line 77: | ||
== Helper Tools == | == Helper Tools == | ||
| − | ; [[Development/Tools/Using kde-config|Get information about KDE's installation - kde-config]] | + | ;[[Development/Tools/Using kde-config|Get information about KDE's installation - kde-config]] |
: The tool kde-config helps to find out more about a KDE installation. | : The tool kde-config helps to find out more about a KDE installation. | ||
| − | ; [[Development/Tools/Using kfmclient|Driving Konqueror From Scripts - kfmclient]] | + | ;[[Development/Tools/Using kfmclient|Driving Konqueror From Scripts - kfmclient]] |
: kfmclient is a small tool to communicate with Konqueror. | : kfmclient is a small tool to communicate with Konqueror. | ||
| Line 98: | Line 100: | ||
: KDE uses [http://www.reviewboard.org/ Review Board] for performing code reviews, see the [[Development/Review_Board|KDE Review Board]] page for more details | : KDE uses [http://www.reviewboard.org/ Review Board] for performing code reviews, see the [[Development/Review_Board|KDE Review Board]] page for more details | ||
| − | ; Continuous Building - Dashboard | + | ;Continuous Building - Dashboard |
: [http://developer.kde.org/~dirk/dashboard/ all kde modules on Dirk's dashboard] | : [http://developer.kde.org/~dirk/dashboard/ all kde modules on Dirk's dashboard] | ||
: [http://winkde.org/pub/kde/ports/win32/dashboard/ some kde software on win32 dashboard] | : [http://winkde.org/pub/kde/ports/win32/dashboard/ some kde software on win32 dashboard] | ||
: [http://public.kitware.com/dashboard.php?name=kde kdelibs on kitware] | : [http://public.kitware.com/dashboard.php?name=kde kdelibs on kitware] | ||
| − | ; [http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis | + | ;[http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis |
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [[Development/Tutorials/Code_Checking|Usage Tutorial]] | : [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [[Development/Tutorials/Code_Checking|Usage Tutorial]] | ||
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics | : [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics | ||
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker | : [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker | ||
: [http://www.englishbreakfastnetwork.org/usability/ Usability Checks] | : [http://www.englishbreakfastnetwork.org/usability/ Usability Checks] | ||
Contents |
Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
This section contains information about tools for KDE development.
A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.
[Development] CheckAccelerators=F12 AutoCheckAccelerators=false AlwaysShowCheckAccelerators=false
> KDE_LANG=x-test kspread
You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of l10n/de/messages/kdebase/konqueror.po:
#: konq_mainwindow.cc:3707 konq_tabs.cc:84 msgid "&New Tab" msgstr "Neues &Unterfenster"
The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from konq_mainwindow.cc and also from konq_tabs.cc. This saves the translators from having to translate the same identical string twice.
You can also use Lokalize to examine .po files. Lokalize is part of the kdesdk module.
| Note |
|---|
| More information on writing and translating documentation can be found on the l10n project site. |
KDE TechBase 