The search section allows you to customize various settings for searching in previous translated strings. There are three pages: General, Parameters and Files.
General settings are common for all search types. If you check Automatically start search option then search is automatically started whenever you switch to another entry in the editor. You can choose where to search in section Default Search. From three items radiobuttons group you can select what search type is default. You can also start searching manually by choosing an entry in the popup menu that appears either when clicking at Tools->Search or keeping the search button in the toolbar pressed for a while.
Default searching setting is used when searching is started automatically or when pressing the search button in the toolbar.
MO-file: MO-files are compiled message files, that are prepared for fast finding a translation. Choosing this you can easily search for similiar translations in message catalogs of a package without having to download the source of this package. This is not implemented yet!
Compendium: The compendium is a normal PO-File, which should contain a list of standard translation from your translation team. If you don't have one, you can also use a file that contains all used translations of your team (e.g. the $lang.messages file in the KDE Project, that can be found at i18n.kde.org).
Auxiliary: The auxiliary should help you finding the context of a translation by looking up the same message in a message catalog of the same package but translated to another language. This way you can have a look how this message is translated in another language.
You can choose here which characters has to be ignored when comparing two strings or if you want to search case sensitive. If you want ignore additional characters, activate option Ignore Other and type in the field behind this button the characters, that has to be ignored. For example, if you type in ?!_ all of this three characters will be ignored. Since searching in a auxiliary is intended to find exactly the same message these options are not used, when searching in the auxiliary.
Here is comprehensive list for these options:
When searching characters case don't matter.
Ignore ampersand character, making possible to match even words which contain ampersand for keyboard accelerator.
Allow to match words which span on multiple lines.
Allow to match words which can contain dots.
In right editline you can write characters desired to be ignored when searching.
is equal to original message
contains original message - e.g.: If the original message is setup, you will get messages displayed like Click to setup
is contained in original message - e.g.: If the original message is Click to setup, you will get messages displayed like setup
First editbox allow you to set language code for the language you are translating in. This is at the moment just useful, if you translate for more than one language and don't want to always have to change the pathes of the files in Locations section. In this case you can use the string @LANG@ in the path to a file, which will then replaced by your language code. Default value for this field is C.
![]() | Strings like @VARIABLE@ represent simple variable to text substitutions. These variables are not related with m4 macro processor! |
Configure what file has to be used when activating search in already compiled PO files. This is last resort if you not have original source for MO files. You should point this path to your locale directory in KDE directory tree. E.g: /opt/kde/share/locale/de/LC_MESSAGES.
Default value: none
Configure what file has to be used when activating search in compendium. The compendium is a normal PO-File, which should contain a list of standard translation from your translation team. If you don't have one, you can also use a file that contains all used translations of your team (e.g. the $lang.messages file in the KDE Project, where $lang is your language code).
Default value: @LANG@.messages
Configure what file has to be used when activating search in auxiliary. The auxiliary should help you finding the context of a translation by looking up the same message in a message catalog of the same package but translated to another language. This way you can have a look how this message is translated in another language. It's very usefull if you speak other language or auxiliary file is somehow related. E.g: french, spanish, romanian. It's very helping because you can find a lot of synonimes.
Default value: ../de/@PACKAGE@.po