kdesdk docs


kbabel_using.po

I've added a few I'm not sure about, denoted (?). The ones I'm least sure about are the "Translation Database" ones. -- AlexWalker

1. #. Tag: para #: using.docbook:477 #, no-c-format
Some of the text are too common and they need to be translated differently in different contexts.
-> Some of the text is too common and needs to be translated differently in different contexts.
If the check founds -> If the check finds

You will probably need this only for &kde; translation. Some of the
text are too common and they need to be translated differently in
different contexts. In &kde; the context is described at the
beginning of <acronym>msgid</acronym> after the special sequence
<userinput>:_</userinput>. But if some translators are not aware of
this convention and they try to translate context information as
well. This check will try to find these. If the check founds
translated context information, you should remove it.

2. #. Tag: para #: using.docbook:576 #, no-c-format
GUI -> GUIs (?)
&kde; project -> The &kde; project (?)

Markup languages are used more and more in <acronym>GUI</acronym>.
&kde; project also uses <acronym>PO</acronym>-files for translating
DocBook documentation files (which is also a markup language).
&kbabel; contains quite a lot of functionality to support this trend.

3. #. Tag: para #: using.docbook:590 #, no-c-format
is capable to find out which tags are used in <acronym>msgid</acronym> and provide an easy access to them
-> is capable of finding out which tags are used in <acronym>msgid</acronym> and providing an easy access to them

The current version of &kbabel; is capable to find out which tags
are used in <acronym>msgid</acronym> and provide an easy access to
them using following actions from the <guimenu>Edit</guimenu>:

4. #. Tag: action #: using.docbook:603 #, no-c-format
inserts next tag -> inserts the next tag

This inserts next tag found in msgid to the translation. &kbabel;
finds the tag to be inserted by counting the number of tags from the
beginning of the translation.

5. #. Tag: action #: using.docbook:620 #, no-c-format
in original english string -> in the original English string
in translated text. translation. -> in the translated text.

This submenu contains all different markup tags found in original
english string. By selecting a tag you can insert it at the current
position of cursor in translated text. translation.

6. #. Tag: para #: using.docbook:633 #, no-c-format
user friendly -> user-friendly

As explained already, current applications, trying to be user
friendly, contain a lot of longer descriptive texts, including
markup. If a developer changes a part of the text, the &GNU; gettext
system will, in the best case, retain the old translation and mark
it as fuzzy. (In the worst case you will lose the translation
completely, depending on the size of the text changes). This works
OK, if a <acronym>msgid</acronym> is short, because then you can
find the changes quickly. But if the text is long enough, you will
struggle to find out what has been changed (For example, it can be
only an article change by proof-reading team.)

7. #. Tag: para #: using.docbook:662 #, no-c-format
set in in -> set in the

As always, you can use different sources for finding the old version
of the text, all being set in in <link linkend=\"preferences-diffmode
\">&kbabel; configuration dialog</link>:

8. #. Tag: para #: using.docbook:670 #, no-c-format
use Translation Database -> use the Translation Database (?)
into Translation Database -> into the Translation Database (?)
in <link linkend=\"database-fill\"> Translation Database configuration dialog</link>
-> in the <link linkend=\"database-fill\">Translation Database configuration dialog</link> (?)

You can use Translation Database for difference lookup. We strongly
recommend to turn on the automatic storing of the newly translated
messages into Translation Database in <link linkend=\"database-fill
\"> Translation Database configuration dialog</link>. This mode can
be turned on by <guilabel>Use messages from Translation Database</
guilabel>.

9. #. Tag: para #: using.docbook:683 #, no-c-format
searching in Translation Database is -> searching in the Translation Database is
A whole load of other things here - I don't even understand what they're trying to say.

This will be used only if searching in Translation Database is
turned off. By setting <guilabel>Base folder for diff files</
guilabel> you can navigate &kbabel;, which file to use for
difference. It takes the relative path of the opened file and uses
this relative path in the folder specified here. If there is a
corresponding file, it will be used. To use this mode, you should
make a copy of old files before each update.

kbabel_glossary.po

1. #. Tag: para #: glossary.docbook:25 #, no-c-format
file so search through -> file to search through

is a &kbabel; specific issue. It is an option for the user to set up
one <acronym>PO</acronym> file so search through for original
messages. For example, if you're a member of French team and have
some Spanish or Italian knowledge you can grab and set-up an
auxiliary Spanish <acronym>PO</acronym> file associated with the
file currently being translated.

2. #. Tag: para #: glossary.docbook:41 #, no-c-format
applications <acronym>PO</acronym> files -> applications' <acronym>PO</acronym> files
into new -> into a new
&kbabel; uses such file in -> &kbabel; uses such files in the

is a collection of all translations for one language. This big
<acronym>PO</acronym> file is made by unique messages from all
applications <acronym>PO</acronym> files. It can be used to fill in
all already translated strings into new yet untranslated or
partially translated <acronym>PO</acronym> file. &kbabel; use such
file in <quote>PO Compendium</quote> search engine.

3. #. Tag: para #: glossary.docbook:140 #, no-c-format
followed by C-like string -> followed by C-like strings

<acronym>msgid</acronym> is the keyword which introduce the original
string in <acronym>PO</acronym> file. It is followed by C-like
string that span on one or multiple lines.

4. #. Tag: para #: glossary.docbook:153 #, no-c-format
which introduce the translated string in <acronym>PO</acronym> file.
-> which introduces the translated string in the <acronym>PO</acronym> file.
followed by C-like string -> followed by C-like strings

<acronym>msgstr</acronym> is the keyword which introduce the
translated string in <acronym>PO</acronym> file. It is followed by C-
like string that span on one or multiple lines.

5. #. Tag: para #: glossary.docbook:169 #, no-c-format
relates only to one language. -> relates to only one language.
is derived from an <acronym>POT</acronym> file -> is derived from a <acronym>POT</acronym> file

<acronym>PO</acronym> stands for <quote>Portable Object</quote>.
<acronym>PO</acronym> files contain sets of strings which associate
each translatable string with its translation in a particular
language. A single <acronym>PO</acronym> file relates to only one
language. A <acronym>PO</acronym> file is derived from an
<acronym>POT</acronym> file and is edited either by hand or using
&kbabel;.