From bd9e6617827818fd043452c08c606f07b78014a0 Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdesdk@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- doc/kbabel/catman.docbook | 214 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 214 insertions(+) create mode 100644 doc/kbabel/catman.docbook (limited to 'doc/kbabel/catman.docbook') diff --git a/doc/kbabel/catman.docbook b/doc/kbabel/catman.docbook new file mode 100644 index 00000000..a55d46ec --- /dev/null +++ b/doc/kbabel/catman.docbook @@ -0,0 +1,214 @@ + + + + + + + + + + + + + + + + + + +Using &catalogmanager; + + + +Screenshot of &catalogmanager; + + + + +Screenshot of &catalogmanager; + + + +The Catalog Manager merges two folders into one tree and displays +all the PO and POT files in +these folders. The display allows you to easily see if a new +template has been added or an old one has been removed. Some +information is shown along with each file name: total number of +entries, number of fuzzy entries, number of untranslated entries, the +date of the last revision and the last translator of the file. + + + +KBabel's Catalog Manager is meant for projects structured like KDE, +where the POT and PO files +share a same name, save the extensions. However this is not the +case of &GNU; projects and of many projects structured like &GNU; ones. +Typically in such projects, the PO file is named +following the language code and so is very different than the name +of the POT files. Also such projects have +one POT file sharing a directory with all its +translated PO files. Unfortunately, all these reasons +mean that the Catalog Manager is not suitable for +such projects. (See KDE bug #76495.) + + + +To make it easier for you to find files that need work or are +missing the status of each file is also displayed using an icon: + + + + + + + + + + All the messages in this file are translated. + + + + + + + + +Some of the messages in this file are fuzzy or untranslated + + + + + + + + + +This file does not exist in the folder of the PO files. + + + + + + + + + +This file contains syntax errors. + + + + + + + + + +Information about this file is being currently updated. When the update is +finished, it will get one of the icons listed above to reflect its state. + + + + + +If an icon is marked with this icon + + + + +, like + + + + +, +it indicates that this file or folder does not exist in the +folder of the POT files. + + You can mark or unmark a file by selecting Toggle +Marking in the context menu of a file. + +If you want to toggle or remove all markings in a folder, +press the right mouse button over the folder and select +Toggle Markings or Remove +Markings. The markings are automatically saved when +leaving &kbabel;. + +To open a file either double-click on the file, select +Open from the +context menu or press either Return or &Ctrl;O . + +You can configure the &catalogmanager; by +Project +Configure.... +See section Project Settings for more +details. + + +&catalogmanager; Features + +Besides the main feature for opening the files in &kbabel; &catalogmanager; +supports number of other features for maintaining a tree of +PO-files. + + + +Find and replace in multiple files + +One of the most requested features for &kbabel; was a possibility to search and replace in +multiple files at once. &catalogmanager; supports this feature with +a tight integration with &kbabel; + + + + +Statistics + +&catalogmanager; can show you a number of statistics about a single file +or about the whole folders. The statistics contain number of files, +how many of the files have their templates, how many templates are missing. +It also counts number of messages in the files and shows statistics about +how large parts of the messages are translated, fuzzy-translated or +untranslated. + + + + +Checking the syntax + +This allows you to check the syntax of multiple PO-files +using msgfmt. If a file fails this check, it cannot +be used for generating a MO-file for binary distribution. +Such an incorrect file will typically result in failing compilation of the package +the PO-file belongs to. + + + + +User-defined commands + +Because &catalogmanager; cannot provide any functionality you would like +to use, you can extend it by defining your own commands. + + + +There are two sets of commands. One for folders and one for single files. +You can set them in configuration dialog and +access by pressing &RMB; on an entry in the file list. + + + + + -- cgit v1.2.1