# translation of kbabel_using.po to 
# translation of kbabel_using.po to
# Copyright (C) 2002 Free Software Foundation, Inc.
# Lwandle Mgidlana <lwandle@translate.org.za>, 2002
#
msgid ""
msgstr ""
"Project-Id-Version: kbabel_using\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: 2002-09-26 12:35+0200\n"
"Last-Translator: Lwandle Mgidlana <lwandle@translate.org.za>\n"
"Language-Team:  <xh@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.0beta2\n"

#: index.docbook:2
#, no-c-format
msgid "Using &kbabel;"
msgstr ""

#: index.docbook:5
#, no-c-format
msgid "Introduction"
msgstr "Ukwazisa"

#: index.docbook:7
#, no-c-format
msgid ""
"Usually program messages and documentation are written in English. Using a "
"framework made from a set of tools and libraries it is posible to have your "
"favorite applications speaking your native non-English language. This "
"process of adapting an application to a specific language is known as "
"localization. The localization process includes translating the program's "
"interfaces and documentation to the various languages users need and, in "
"some countries or regions, making the inputs and outputs conform to "
"particular conventions. &kbabel; is a tool which will assist you in the "
"internationalization process to make an application's interface speak many "
"languages."
msgstr ""

#: index.docbook:18
#, no-c-format
msgid ""
"Every internationalization-aware program makes available for translation one "
"or more message-catalog files. The extension of these files is <literal "
"role=\"extension\">.pot</literal>. <acronym>POT</acronym> is an acronym for "
"<quote>Portable Object Template</quote>."
msgstr ""

#: index.docbook:25
#, no-c-format
msgid ""
"Every translator takes a <acronym>POT</acronym> file copy and begins "
"translating messages. That, this file will became a <acronym>PO</acronym> "
"file - Portable Object and represents only one language."
msgstr ""

#: index.docbook:30
#, no-c-format
msgid ""
"Each translator takes a copy of one of these POT templates and begins "
"filling in the blanks: each message is translated into the language desired. "
"The file containing the translated text is referred to as a "
"<acronym>PO</acronym> (Portable Object) file."
msgstr ""

#: index.docbook:35
#, no-c-format
msgid ""
"Once all the messages have been translated the <acronym>PO</acronym>"
" file is compiled into a machine-readable binary format, known as a "
"<acronym>MO</acronym> (Machine Object) file. These files, which will be "
"stored with a <literal role=\"extension\">.mo</literal> extension, act as a "
"database to minimize the time taken by the applications to look up each "
"translated message."
msgstr ""

#: index.docbook:43
#, no-c-format
msgid ""
"There is a question in the air: do I need to know what is inside a "
"<acronym>PO</acronym> file even though I have &kbabel;? The answer is, "
"undoubtfully, yes. There are situations when a message catalog can become "
"corrupt and needs to be manually fixed. Most of these problems are the "
"so-hated <acronym>CVS</acronym> conflicts which occur when a translating "
"process is coordinated by a concurent version system (see the <ulink "
"url=\"info:/cvs\">CVS</ulink> documentation). &kbabel; can't help you very "
"much if a problem like this arises so a text editor some knowledge of "
"<acronym>PO</acronym>-files is needed. Let's see how a <acronym>PO</acronym>"
" file is made."
msgstr ""

#: index.docbook:54
#, no-c-format
msgid ""
"<acronym>PO</acronym> files consist of pairs of messages&mdash;a "
"<emphasis>msgid</emphasis> and a <emphasis>msgstr</emphasis>. The msgid is "
"the text in English and the msgstr is the text translated into the "
"appropriate language. The text that accompanies each msgid and msgstr is "
"enclosed within C-like double quotes. An example, taken from a "
"<acronym>PO</acronym> file for &noatun;, is <literal>msgid &quot;Open a "
"Playlist&quot;</literal>"
msgstr ""

#: index.docbook:62
#, no-c-format
msgid ""
"Empty lines and those starting with <literal>#</literal> are ignored. Lines "
"starting with a # represent comments and are a useful means of providing a "
"note detailing which file this message is going to be used in and, in the "
"case of the application writers, to provide additional comments to aide "
"translation. &kbabel; displays these comment lines for every message."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"In many cases the first msgid-msgstr pair in <acronym>PO</acronym>"
" file is a fake entry (acting as <acronym>PO</acronym> file header) that "
"contains various information about the translated <acronym>PO</acronym> "
"file, such as the application name, translating date, translator name and so "
"on."
msgstr ""

#: index.docbook:75
#, no-c-format
msgid ""
"Recent versions of <application>&GNU; gettext</application> added another "
"usefull i18n feature called <emphasis>plural forms</emphasis>. English uses "
"only singular and one plural form of nouns, &eg; <quote>1 file </quote> and "
"<quote>10 files</quote>"
". This leads many developers to an idea that world is that simple and they "
"can use messages like <quote>Do you want to delete %1 file(s)?</quote>, "
"where <literal>%1</literal> denotes a number of files to be deleted. But "
"this is fundamentally wrong. For Slovak translation you need 3 different "
"forms of the message. This number is different for different languages and "
"even if it is the same, &eg; Czech uses 3 forms as well, a rule to decide "
"which form to use can be very different."
msgstr ""

#: index.docbook:88
#, no-c-format
msgid ""
"Plural forms in <acronym>PO</acronym>"
" files are here to help. Unfortunately, &kde; developers do not like the "
"plural forms implementation in <application>&GNU; gettext</application> and "
"they introduces their own format and handling for them."
msgstr ""

#: index.docbook:97
#, no-c-format
msgid "Editor"
msgstr "Umhleli"

#: index.docbook:99
#, no-c-format
msgid ""
"Here is a screenshot of &kbabel;. For convenience &kbabel; has toolbars to "
"speed up many operations and, for busy users, there are many keyboard "
"shortcuts. The main window is divided into four parts."
msgstr ""

#: index.docbook:104
#, no-c-format
msgid ""
"The <emphasis>upper-left</emphasis> edit box is read-only and contains the "
"current msgid field from the opened PO-file and its English text."
msgstr ""

#: index.docbook:108
#, no-c-format
msgid ""
"The <emphasis>bottom-left</emphasis> edit box contains the msgstr field "
"related to the msgid shown and here you can edit the translated text."
msgstr ""

#: index.docbook:112
#, no-c-format
msgid ""
"The <emphasis>top-right</emphasis> part of the window is a comments panel "
"where you can view the comments added for entry currently being edited."
msgstr ""

#: index.docbook:116
#, no-c-format
msgid "It can be used:"
msgstr ""

#: index.docbook:118
#, no-c-format
msgid ""
"to find out how the current message is treated by the application "
"(c-formatted or simple)"
msgstr ""

#: index.docbook:118
#, no-c-format
msgid ""
"in some cases to read helpful comments added by the application's developer "
"to assist the translators in their work&mdash;for example, there may be "
"technical hints (used to great effect in the <application>LyX</application> "
"project)"
msgstr ""

#: index.docbook:118
#, no-c-format
msgid ""
"when you need to know from what file current messages is because you want to "
"report a spelling mistake in the original English string."
msgstr ""

#: index.docbook:135
#, no-c-format
msgid "Screenshot of &kbabel;"
msgstr ""

#: index.docbook:145
#, no-c-format
msgid ""
"The editor window (in the bottom right) is the most sophisticated part of "
"&kbabel;'s main window. Its size can be adjusted using the splitter line "
"between it and the comment panel (the panel in the top right). The editor "
"window has two tabbed panels&mdash;one storing search information, the other "
"context information. The context information tab contain a scrolled view "
"which shows the previous and next 4 entries associated with the current "
"entry&mdash;essentially it's a small 'snapshot' of the PO file. While "
"translating it is very common for message strings to be related to "
"subsequent and previous messages, so the context panel is useful for looking "
"at the nearby messages to get an indication as to how the current message "
"can best be translated. Dialog interface translation is a good example or "
"widgets with their associated text and \"what's this\" message."
msgstr ""

#: index.docbook:163
#, no-c-format
msgid "More &kbabel; Features"
msgstr ""

#: index.docbook:165
#, no-c-format
msgid "Each msgid entry can be in three states:"
msgstr ""

#: index.docbook:169
#, no-c-format
msgid "untranslated"
msgstr "engaguqulwanga kolunye ulwimi"

#: index.docbook:169
#, no-c-format
msgid "there is no translated text currently associated with the msgstr"
msgstr ""

#: index.docbook:169
#, no-c-format
msgid "fuzzy"
msgstr "engagqibekanga"

#: index.docbook:169
#, no-c-format
msgid ""
"<command>msgmerge</command> has tried to match a translated string by "
"looking in rest of PO-file entries. This does not work perfectly and you "
"must edit the translated text to fit the current English text."
msgstr ""

#: index.docbook:169
#, no-c-format
msgid "translated"
msgstr ""

#: index.docbook:169
#, no-c-format
msgid "the msgid is the completed translated form of the msgstr"
msgstr ""

#: index.docbook:199
#, no-c-format
msgid ""
"The state of the current entry is indicated by two <acronym>LED</acronym>s. "
"Depending on your configuration these can either be in the status bar or "
"above the <guilabel>translated string</guilabel> edit box. Both have a "
"customizable color (to reflect your visual requirements or taste). Please "
"read the <link linkend=\"preferences\">Preferences</link>"
" section to see how you can adjust these settings."
msgstr ""

#: index.docbook:212
#, no-c-format
msgid "Advanced Translation"
msgstr ""

#: index.docbook:214
#, no-c-format
msgid ""
"Now you have an idea how to translate a PO-file. In this section we will "
"follow standard way for translating a new PO-file using the advanced "
"features of &kbabel;. We assume you have already opened a template POT-file "
"and saved as PO file."
msgstr ""

#: index.docbook:221
#, no-c-format
msgid "Navigation in PO-file"
msgstr ""

#: index.docbook:222
#, no-c-format
msgid ""
"&kbabel; allows you to easily navigate through the file according to the "
"state of their translation. The untranslated/fuzzy status was introduced "
"already. A message can be marked as errorneous as a result of <link "
"linkend=\"kbabel-validation\">validation checking</link> or validation done "
"by <command>msgfmt</command>. And, of course, &kbabel; supports the history "
"of visited messages by <guilabel>Forward</guilabel>/<guilabel> "
"Back</guilabel> similar to &konqueror;."
msgstr ""

#: index.docbook:227
#, no-c-format
msgid ""
"All commands for navigation are in "
"<menuchoice><guimenu>Go</guimenu></menuchoice> menu."
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Page Up"
msgstr "Iphepha Eliphezulu"

#: index.docbook:232
#, no-c-format
msgid "Move to the previous message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Page Down"
msgstr "Iphepha Ezantsi"

#: index.docbook:232
#, no-c-format
msgid "Move to the next message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Ctrl;<keycap>Page Up</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the previous fuzzy message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Ctrl;<keycap>Page Down</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the next fuzzy message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Alt;<keycap>Page Up</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the previous untranslated message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Alt;<keycap>Page Down</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the next untranslated message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Shift;<keycap>Page Up</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the previous error message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Shift;<keycap>Page Down</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the next error message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Ctrl;&Shift;<keycap>Page Up</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the previous fuzzy or untranslated message"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "&Ctrl;&Shift;<keycap>Page Down</keycap>"
msgstr ""

#: index.docbook:232
#, no-c-format
msgid "Move to the next fuzzy or untranslated message"
msgstr ""

#: index.docbook:280
#, no-c-format
msgid "Clever editing"
msgstr ""

#: index.docbook:281
#, no-c-format
msgid ""
"<emphasis>Clever editing</emphasis> means that the editor will help you "
"easily edit the translation while taking into account specials of the PO "
"format. It will correctly <quote>escape</quote> as necessary."
msgstr ""

#: index.docbook:284
#, no-c-format
msgid ""
"It also supports more than one mode for inserting end of the line. This is "
"very useful because of the way gettext handles end of the lines. It simply "
"ignores them. (You can imagine that all the text in "
"<acronym>msgstr</acronym> is a single line.) If you want insert a "
"<quote>real</quote> end of the line, you need to insert "
"<userinput>\\n</userinput>. But most of translators do not realize, that a "
"new line in <acronym>msgstr</acronym> does not add any space between the "
"lines. This can be easily solved by adding a space at the end of every line. "
"But you can easily forget, so clever editing does this automatically for you."
msgstr ""

#: index.docbook:295
#, no-c-format
msgid "The table below summarizes clever editing features."
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "<keycap>Tab</keycap>"
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "Insert <emphasis>\\t</emphasis>"
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "<keycap>\"</keycap>"
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "Insert <emphasis>\\\"</emphasis>"
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "Enter"
msgstr "Faka"

#: index.docbook:300
#, no-c-format
msgid ""
"If the last character before cursor is not a space, insert one space. Then "
"start a new line."
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "&Ctrl;<keycap>Enter</keycap>"
msgstr "&Ctrl;<keycap>Ngena</keycap>"

#: index.docbook:300
#, no-c-format
msgid "Start a new line without any additional logic"
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "&Shift;<keycap>Enter</keycap>"
msgstr ""

#: index.docbook:300
#, no-c-format
msgid "Insert <emphasis>\\n</emphasis> and start a new line"
msgstr ""

#: index.docbook:324
#, no-c-format
msgid ""
"If you wnat to see where are spaces, you can turn on <guibutton>Highlight "
"background</guibutton> and/or <guibutton>Mark whitespaces with "
"points</guibutton> in preferences dialog on tab <guilabel>Edit</guilabel> "
"<guilabel>Appearance</guilabel>."
msgstr ""

#: index.docbook:334
#, no-c-format
msgid "Automatic translation"
msgstr ""

#: index.docbook:335
#, no-c-format
msgid ""
"As the first step when starting a new translation, &kbabel; provides "
"function for automatic filling of the messages translations by the older "
"translations. Choose <menuchoice><guimenu>Tools</guimenu><guimenuitem>Rough "
"Translation</guimenuitem> </menuchoice> and &kbabel; will present the "
"following dialog:"
msgstr ""

#: index.docbook:341
#, no-c-format
msgid "Rough translation dialog"
msgstr ""

#: index.docbook:351
#, no-c-format
msgid ""
"In the dialog, you should specify what to translate and choose the sources "
"for the old translations."
msgstr ""

#: index.docbook:355
#, no-c-format
msgid ""
"At the top of the <guilabel>What to translate</guilabel> frame are three "
"checkboxes (<guilabel>Untranslated entries</guilabel>, <guilabel>Fuzzy "
"entries </guilabel>, <guilabel>Translated entries</guilabel>"
") for specifying the kind of messages you want to translate. Untranslated "
"and fuzzy entries are natural choices for automatic translation, but you can "
"change already translated messages as well."
msgstr ""

#: index.docbook:363
#, no-c-format
msgid ""
"The exact matching for <acronym>msgid</acronym>s will be used for rough "
"translation always. However, you can add more strategies, &ie; "
"<guilabel>Allow fuzzy translation (slow)</guilabel> and <guilabel>Allow "
"single word translation</guilabel>"
". Both of these additional strategies must be supported by the sources used "
"(see below). There is no specification, what does <quote>fuzzy "
"translation</quote> mean, but the purpose is quite obvious. <quote>Single "
"word translation</quote> is suitable for only some of the languages. "
"&kbabel; will try to translate each word in <acronym>msgid</acronym> "
"separately and then put the translated words (or phrases) in the same order "
"in <acronym>msgstr </acronym>."
msgstr ""

#: index.docbook:376
#, no-c-format
msgid ""
"As a source for rough translation, any dictionary module available can be "
"used. There is a list of <guilabel>Don't use</guilabel> modules and "
"<guilabel>Use</guilabel> modules. Modules are used in the order in the "
"<guilabel>Use</guilabel> list. First module is asked for translation. If it "
"is not found, next module in the list is asked and so on. You can use the "
"buttons with arrows for moving modules between the lists. Don't forget to "
"change the order to suit your needs by <guibutton>Move Up </guibutton> and "
"<guibutton>Move Down</guibutton> buttons."
msgstr ""

#: index.docbook:386
#, no-c-format
msgid ""
"Normally &kbabel; will mark every roughly translated message as fuzzy, "
"because it assumes that any automatic translation needs to be reviewed by a "
"translator. If you are 100% sure that the automatic translation will be "
"correct, or you will review all the translation anyway. <guilabel>Mark "
"changed entries as fuzzy</guilabel> allows you to turn off this automatic "
"fuzzy marking, but you will need to confirm this."
msgstr ""

#: index.docbook:394
#, no-c-format
msgid ""
"If you have set all the options to suit your needs, push <guibutton>Start "
"</guibutton> to automatically translate messages. You can follow the "
"progress bar and in case, there is always the <guibutton>Stop</guibutton> "
"button."
msgstr ""

#: index.docbook:403
#, no-c-format
msgid "Validate your translation"
msgstr ""

#: index.docbook:404
#, no-c-format
msgid ""
"Everyone makes mistakes. So &kbabel; supports number of checks for typical "
"problems in translations. These checks (not syntax check) can be basically "
"performed in two ways."
msgstr ""

#: index.docbook:407
#, no-c-format
msgid ""
"Checks can be done at each change of the translated text. These are called "
"<emphasis>automatic</emphasis> checks and they can be turned on in <link "
"linkend=\"preferences-editor\">the &kbabel; configuration dialog</link>. "
"Automatic checking of syntax is possible at each saving of the file."
msgstr ""

#: index.docbook:413
#, no-c-format
msgid ""
"The automatic checks can slow down &kbabel;. If you have a slower computer, "
"you can turn off the automatic checks and use only the second possibility. "
"You can invoke every kind of check from the "
"<menuchoice><guimenu>Tools</guimenu><guisubmenu> "
"Validation</guisubmenu></menuchoice>. Then the check is performed for all "
"messages in the file and faulty ones are marked as errors."
msgstr ""

#: index.docbook:421
#, no-c-format
msgid "Check Syntax"
msgstr ""

#: index.docbook:421
#, no-c-format
msgid ""
"This invokes <command>msgfmt</command> to check validity of the PO file as "
"seen by gettext package. It will show the result of the command and mark "
"error <acronym>msgstr</acronym>s."
msgstr ""

#: index.docbook:421
#, no-c-format
msgid "Check Arguments"
msgstr ""

#: index.docbook:421
#, no-c-format
msgid ""
"Incorrect translations can crash the application. The most dangerous parts "
"of translation are arguments, &eg; for printf-like functions. This check "
"compares the number and types of the arguments in <acronym>msgid</acronym> "
"and <acronym>msgstr</acronym>. They must match."
msgstr ""

#: index.docbook:421
#, no-c-format
msgid "Check Accelerators"
msgstr ""

#: index.docbook:421
#, no-c-format
msgid ""
"GUI text commonly contain accelerators, &ie; letters which can be used for "
"fast access to GUI elements by keyboard. They are denoted by special "
"character, &eg; &amp; in &kde;. Typical requirement of the translation is "
"that translated text should contain accelerator as well. This check will "
"notice this problem for you. The accelerator character can be specified in "
"<guilabel>Preferences</guilabel> on <guilabel>Misc</guilabel> tab."
msgstr ""

#: index.docbook:421
#, no-c-format
msgid "Look for Translated Context Info"
msgstr ""

#: index.docbook:421
#, no-c-format
msgid ""
"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; is context 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 it founds "
"translated context info, you should remove it."
msgstr ""

#: index.docbook:421
#, no-c-format
msgid "Check Plural Forms"
msgstr ""

#: index.docbook:421
#, no-c-format
msgid ""
"If the <acronym>msgid</acronym> is specified as a <quote>plural "
"form</quote>, the translation has to contain the correct number of "
"translations separated by <userinput>\\n</userinput>. The correct number "
"depends on the language of translation and is specified on "
"<guilabel>Identity</guilabel> tab in <guilabel> Preferences</guilabel> "
"dialog. This is implemented only for &kde; at the moment."
msgstr ""

#: index.docbook:421
#, no-c-format
msgid "Check Equations"
msgstr ""

#: index.docbook:421
#, no-c-format
msgid ""
"Equations are special format of <acronym>msgid</acronym> typically used in "
".desktop files. And because your translations will be merged back to these "
"files, <acronym>msgstr</acronym> must use this special format as well. This "
"means that the translation must start (up to the first occurence of "
"<literal>=</literal> with the same text as the original message, &eg; "
"<userinput>Name=</userinput>."
msgstr ""

#: index.docbook:497
#, no-c-format
msgid "Spellchecking the translation"
msgstr ""

#: index.docbook:498
#, no-c-format
msgid ""
"As always, it is very important to spell check your translation before using "
"your result. This way you can find typos and other problems in your "
"translation. &kbabel; uses the standard &kde; library for spellchecking and "
"its standard configuration can found in <link "
"linkend=\"preferences-spellcheck\">the &kbabel; configuration dialog</link>"
". Spell checking itself can be found in "
"<menuchoice><guimenu>Tools</guimenu><guisubmenu>Spelling</guisubmenu> "
"</menuchoice> submenu. You can use a number of modes for spell checking:"
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Spell check..."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid ""
"This is a generic invocation of a dialog, where you can choose the "
"spellchecking mode and set a default mode, which is invoked by a <keycombo "
"action=\"simul\">&Ctrl;<keycap>I</keycap> </keycombo>."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Check All..."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Spellcheck all messages in the file."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Spell from Cursor Position..."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid ""
"Start spellchecking at the position in the current message and progress "
"towards the end of the file."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Check Current..."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Spellcheck the current message only."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid "Check Selected Text..."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid ""
"If there is a selected text in <acronym>msgstr</acronym>"
" editor, this option is available and will spellcheck this text only."
msgstr ""

#: index.docbook:557
#, no-c-format
msgid "Translating &XML;, <acronym>HTML</acronym>, ..."
msgstr ""

#: index.docbook:558
#, no-c-format
msgid ""
"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."
msgstr ""

#: index.docbook:564
#, no-c-format
msgid ""
"Here, we will describe only functions related to tags used for markup "
"itself. The other problem introduced by using markup languages is "
"translation of longer texts. This issue is addressed by the "
"<emphasis>diff</emphasis> feature described in <link "
"linkend=\"kbabel-diff\">the following section</link>."
msgstr ""

#: index.docbook:572
#, no-c-format
msgid ""
"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>:"
msgstr ""

#: index.docbook:578
#, no-c-format
msgid "Insert Next Tag"
msgstr ""

#: index.docbook:578
#, no-c-format
msgid ""
"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."
msgstr ""

#: index.docbook:578
#, no-c-format
msgid "<guimenu>Edit</guimenu> <guisubmenu>Insert Tag</guisubmenu>"
msgstr ""

#: index.docbook:578
#, no-c-format
msgid ""
"This submenu contains all different markup tags found in original english "
"string. By selecting one of them you can insert at the current position of "
"cursor in translated text. translation."
msgstr ""

#: index.docbook:614
#, no-c-format
msgid "Showing the difference"
msgstr ""

#: index.docbook:615
#, no-c-format
msgid ""
"As we said 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 better case, "
"retain the old translation and mark it as fuzzy. (In worse case you will "
"loose the translation completely, depending on the size of the text "
"changes). This works OK, if a <acronym>msgid</acronym> is short, because "
"them 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.)"
msgstr ""

#: index.docbook:625
#, no-c-format
msgid ""
"To help, &kbabel; can be asked to lookup the original "
"<acronym>msgid</acronym> and to show the difference. The changes are "
"graphically displayed in the <guilabel>Original String</guilabel> editor. "
"The exact way can be set in the <link "
"linkend=\"preferences-editor-appearance\">&kbabel; configuration "
"dialog</link>. <menuchoice><guimenu>Tools</guimenu> "
"<guisubmenu>Diff</guisubmenu> <guimenuitem>Show Diff</guimenuitem> "
"</menuchoice> will show the differences found. To see the current text "
"without the mix with the original text, use "
"<menuchoice><guimenu>Tools</guimenu> <guisubmenu>Diff</guisubmenu> "
"<guimenuitem>Show Original Text</guimenuitem> </menuchoice>."
msgstr ""

#: index.docbook:637
#, no-c-format
msgid ""
"You can turn on and off automatic lookup of difference by choosing "
"<menuchoice><guimenu>Tools</guimenu> <guisubmenu>Diff</guisubmenu> "
"<guimenuitem>Diff Mode</guimenuitem> </menuchoice>. When the diff mode is "
"on, difference searching starts when you go to another message."
msgstr ""

#: index.docbook:644
#, no-c-format
msgid ""
"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>:"
msgstr ""

#: index.docbook:648
#, no-c-format
msgid "Translation Database"
msgstr ""

#: index.docbook:648
#, no-c-format
msgid ""
"You can use Translation Database for difference lookup. We strongly "
"recommend to turned on 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>."
msgstr ""

#: index.docbook:648
#, no-c-format
msgid "Tree of the old files"
msgstr ""

#: index.docbook:648
#, no-c-format
msgid ""
"This will be used only if searching in Translation Database is turned off. "
"By setting <guilabel>Base directory 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 directory "
"specified here. If there is a corresponding file, it will be used. To you "
"this mode, you should make a copy of old files before each update."
msgstr ""

#: index.docbook:648
#, no-c-format
msgid "Manually chosen file"
msgstr ""

#: index.docbook:648
#, no-c-format
msgid ""
"If the previous possibility do not work, correctly, you can always set the "
"difference file manually by choosing <menuchoice> "
"<guimenu>Tools</guimenu><guisubmenu>Diff</guisubmenu> <guimenuitem>"
"Open File for Diff</guimenuitem></menuchoice>."
msgstr ""

#: index.docbook:688
#, no-c-format
msgid ""
"The difference lookup is not always accurate, because the "
"<acronym>PO</acronym>-file does not contain any reference to the original "
"message."
msgstr ""

#: index.docbook:700
#, no-c-format
msgid "Plural Forms"
msgstr ""

#: index.docbook:701
#, no-c-format
msgid ""
"Because plural forms are quite a complicated issue, we devote a special "
"section for their suport in &kbabel;."
msgstr ""

#: index.docbook:705
#, no-c-format
msgid ""
"&kbabel; can read the &GNU; plural forms only, but cannot edit them. It only "
"supports &kde; version of plural forms at the moment."
msgstr ""

#: index.docbook:709
#, no-c-format
msgid ""
"Every language, to which &kde; is translated, must have set a correct number "
"of plural forms. This is done by translating an entry in "
"<filename>kdelibs.po</filename>. The number is set by selecting the name of "
"a language, which uses the same number and <emphasis>rules</emphasis> for "
"finding the right plural form. The up-to-date list of possible values can be "
"found in the kdelibs source code, in the file "
"<filename>kdecore/klocale.cpp</filename>."
msgstr ""

#: index.docbook:717
#, no-c-format
msgid ""
"&kde; plural forms are denoted by comment <userinput>_:</userinput> "
"containing the <literal>%n</literal>"
" argument. This argument is then used in the message itself and it controls "
"which plural form of your language should be used depending on the rules for "
"your language."
msgstr ""

#: index.docbook:723
#, no-c-format
msgid ""
"The translation of a plural form message has to have a special format. It "
"must contain the correct number of translations (one for each plural form) "
"separated by an end of the line <literal>\\n</literal>. For example, "
"<quote>Selected %n files</quote> translated to Slovak would be:"
msgstr ""

#: index.docbook:729
#, no-c-format
msgid ""
"Vybraný %n súbor\\n\n"
"Vybrané %n súbory\\n\n"
"Vybraných %n súborov"
msgstr ""

#: index.docbook:734
#, no-c-format
msgid ""
"To check, if your translation contain correct number of plural forms, use "
"the <menuchoice><guimenu>Tools</guimenu> <guisubmenu>Validation "
"</guisubmenu> <guimenuitem>Check Plural Forms (KDE only)</guimenuitem> "
"</menuchoice> menu."
msgstr ""
