# translation of KRegExpEditor.po to 
# translation of KRegExpEditor.po to
# Copyright (C) 2002 Free Software Foundation, Inc.
# Lwandle Mgidlana <lwandle@translate.org.za>, 2002
#
msgid ""
msgstr ""
"Project-Id-Version: KRegExpEditor\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: 2002-09-26 12:36+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:10
#, no-c-format
msgid "The Regular Expresion Editor Manual"
msgstr ""

#: index.docbook:13
#, no-c-format
msgid ""
"<firstname>Jesper K.</firstname> <surname>Pedersen</surname> "
"<affiliation><address><email>blackie@kde.org</email></address></affiliation>"
msgstr ""

#: index.docbook:27
#, no-c-format
msgid "Jesper K. Pedersen"
msgstr ""

#: index.docbook:31
#, no-c-format
msgid "This Handbook describes the Regular Expression Editor widget"
msgstr ""

#: index.docbook:35
#, no-c-format
msgid "<keyword>KDE</keyword>"
msgstr "<keyword>KDE</keyword>"

#: index.docbook:36
#, no-c-format
msgid "regular expression"
msgstr "ukuzichaza rhoqo"

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

#: index.docbook:47
#, no-c-format
msgid ""
"The regular expression editor is an editor for editing regular expression in "
"a graphical style (in contrast to the ascii syntax). Traditionally regular "
"expressions have been typed in the ascii syntax, which for example looks "
"like <literal>^.*kde\\b</literal>. The major drawback of this style is:"
msgstr ""

#: index.docbook:47
#, no-c-format
msgid "It is hard to understand for non-programmers."
msgstr ""

#: index.docbook:47
#, no-c-format
msgid ""
"It requires that you <emphasis>escapes</emphasis> certain symbols (to match "
"a star for example, you need to type <literal>\\*</literal>)."
msgstr ""

#: index.docbook:47
#, no-c-format
msgid ""
"It requires that you remember rules for <emphasis>precedence</emphasis> "
"(What does <literal>x|y*</literal> match? a single <literal>x</literal>"
" or a number of <literal>y</literal>, <emphasis>OR</emphasis> a number of "
"<literal>x</literal> and <literal>y</literal>'s mixed?)"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"The regular expression editor, on the other hand, lets you "
"<emphasis>draw</emphasis>"
" your regular expression in an unambiguous way. The editor solves at least "
"item two and three above. It might not make regular expressions available "
"for the non-programmers, though only tests by users can tell that. So, are "
"you a non programmer, which have gained the power of regular expression from "
"this editor, then please <ulink url=\"mailto:blackie@kde.org\">let me "
"know</ulink>."
msgstr ""

#: index.docbook:85
#, no-c-format
msgid "What is a Regular Expression"
msgstr ""

#: index.docbook:87
#, no-c-format
msgid ""
"Regular expression is a way to specify <emphasis>conditions</emphasis>"
" to be fulfilled for a situation in mind. Normally when you search in a text "
"editor you specify the text to search for <emphasis>literally</emphasis>, "
"using regular expression, on the other hand, you tell what a given match "
"would look like. Examples of this includes <emphasis>I'm searching for the "
"word KDE, but only at the beginning of the line</emphasis>, or <emphasis>"
"I'm searching for the word <literal>the</literal>, but it must stand on its "
"own</emphasis>, or <emphasis>I'm searching for files starting with the word "
"<literal>test</literal>, followed by a number of digits, for example "
"<literal>test12</literal>, <literal>test107</literal> and "
"<literal>test007</literal></emphasis>"
msgstr ""

#: index.docbook:100
#, no-c-format
msgid ""
"You build regular expressions from sub regular expression, just like you "
"build large Lego toys from smaller subparts. As in the Lego world, there are "
"a number of basic building blocks. In the following I will describe each of "
"these basic building blocks using a number of examples."
msgstr ""

#: index.docbook:106
#, no-c-format
msgid "Searching for normal text."
msgstr ""

#: index.docbook:106
#, no-c-format
msgid ""
"If you just want to search for a given text, then regular expression is "
"definitely not a good choice. The reason for this is that regular "
"expressions assign special meaning to some characters. This includes the "
"following characters: <literal>.*|$</literal>. Thus if you want to search "
"for the text <literal>kde.</literal> (i.e. the characters "
"<literal>kde</literal>"
" followed by a period), then you would need to specify this as "
"<literal>kde\\.</literal><footnote><para>The regular expression editor "
"solves this problem by taking care of escape rules for "
"you.</para></footnote> Writing <literal>\\.</literal> rather than just "
"<literal>.</literal> is called <emphasis>escaping</emphasis>."
msgstr ""

#: index.docbook:121
#, no-c-format
msgid "Matching URL's"
msgstr ""

#: index.docbook:121
#, no-c-format
msgid ""
"When you select something looking like a URL in KDE, then the program "
"<command>klipper</command> will offer to start <command>konqueror</command> "
"with the selected URL."
msgstr ""

#: index.docbook:121
#, no-c-format
msgid ""
"<command>Klipper</command> does this by matching the selection against "
"several different regular expressions, when one of the regular expressions "
"matches, the accommodating command will be offered."
msgstr ""

#: index.docbook:121
#, no-c-format
msgid ""
"The regular expression for URLs says (among other things), that the "
"selection must start with the text <literal>http://</literal>. This is "
"described using regular expressions by prefixing the text "
"<literal>http://</literal> with a hat (the <literal>^</literal> character)."
msgstr ""

#: index.docbook:121
#, no-c-format
msgid ""
"The above is an example of matching positions using regular expressions. "
"Similar, the position <emphasis>end-of-line</emphasis> can be matched using "
"the character <literal>$</literal> (i.e. a dollar sign)."
msgstr ""

#: index.docbook:143
#, no-c-format
msgid ""
"Searching for the word <literal>the</literal>, but not "
"<emphasis>the</emphasis><literal>re</literal>, "
"<literal>brea</literal><emphasis>the</emphasis> or "
"<literal>ano</literal><emphasis>the</emphasis><literal>r</literal>"
msgstr ""

#: index.docbook:143
#, no-c-format
msgid ""
"Two extra position types can be matches in the above way, namely "
"<emphasis>the position at a word boundary</emphasis>, and <emphasis>the "
"position at a <emphasis>non</emphasis>-word boundary</emphasis>. The "
"positions are specified using the text <literal>\\b</literal> (for "
"word-boundary) and <literal>\\B</literal> (for non-word "
"boundary)<emphasis></emphasis>"
msgstr ""

#: index.docbook:143
#, no-c-format
msgid ""
"Thus, searching for the word <literal>the</literal> can be done using the "
"regular expression <literal>\\bthe\\b</literal>. This specifies that we are "
"searching for <literal>the</literal> with no letters on each side of it "
"(i.e. with a word boundary on each side)"
msgstr ""

#: index.docbook:143
#, no-c-format
msgid ""
"The four position matching regular expressions are inserted in the regular "
"expression editor using <link linkend=\"positiontool\">four different "
"positions tool</link>"
msgstr ""

#: index.docbook:165
#, no-c-format
msgid "Searching for either <literal>this</literal> or <literal>that</literal>"
msgstr ""

#: index.docbook:165
#, no-c-format
msgid ""
"Imagine that you want to run through your document searching for either the "
"word <literal>this</literal> or the word <literal>that</literal>. With a "
"normal search method you could do this in two sweeps, the first time around, "
"you would search for <literal>this</literal>"
", and the second time around you would search for <literal>that</literal>."
msgstr ""

#: index.docbook:165
#, no-c-format
msgid ""
"Using regular expression searches you would search for both in the same "
"sweep. You do this by searching for <literal>this|that</literal>. I.e. "
"separating the two words with a vertical bar."
msgstr ""

#: index.docbook:165
#, no-c-format
msgid ""
"Note on each side of the vertical bar is a regular expression, so this "
"feature is not only for searching for two different pieces of text, but for "
"searching for two different regular expressions."
msgstr ""

#: index.docbook:165
#, no-c-format
msgid ""
"In the regular expression editor you do not write the vertical bar yourself, "
"but instead select the <link linkend=\"altntool\">alternative tool</link>, "
"and inserts the sub regular expressions above each other."
msgstr ""

#: index.docbook:187
#, no-c-format
msgid "Matching anything"
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"Regular expressions are often compared to wildcard matching in the shell - "
"that is the capability to specify a number of files using the asterisk. You "
"will most likely recognize wildcard matching from the following examples:"
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"<literal>rm *~</literal> - here <literal>*~</literal> is the shell wildcard "
"matching every file ending in <literal>~</literal>"
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"cat test??.res - matching every file starting with <literal>test</literal> "
"followed by two arbitrary characters, and finally followed by the test "
"<literal>.res</literal>"
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"In the shell the asterisk matches any character any number of times. In "
"other word, the asterisk matches <emphasis>anything</emphasis>. This is "
"written like <literal>.*</literal> with regular expression syntax. The dot "
"matches any single character, i.e. just <emphasis>one</emphasis> character, "
"and the asterisk, says that the regular expression prior to it should be "
"matched any number of times. Together this says any single character any "
"number of times."
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"This may seem overly complicated, but when you get the larger picture you "
"will see the power. Let me show you another basic regular expression: "
"<literal>a</literal>. The letter <literal>a</literal> on its own is a "
"regular expression that matches a single letter, namely the letter "
"<literal>a</literal>. If we combine this with the asterisk, i.e. "
"<literal>a*</literal>"
", then we have a regular expression matching any number of a's."
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"We can combine several regular expression after each other, for example "
"<literal>ba(na)*</literal>. <footnote><para><literal>(na)*</literal> just "
"says that what is inside the parenthesis is repeated any number of "
"times.</para></footnote> Imagine you had typed this regular expression into "
"the search field in a text editor, then you would have found the following "
"words (among others): <literal>ba</literal>, <literal>bana</literal>, "
"<literal>banana</literal>, <literal>bananananananana</literal>"
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"Given the information above, it hopefully isn't hard for you to write the "
"shell wildcard <literal>test??.res</literal>"
" as a regular expression Answer: <literal>test..\\.res</literal>"
". The dot on its own is any character. To match a single dot you must write "
"<literal>\\.</literal><footnote><para>This is called "
"escaping</para></footnote>. In other word, the regular expression "
"<literal>\\.</literal> matches a dot, while a dot on its own matches any "
"character."
msgstr ""

#: index.docbook:187
#, no-c-format
msgid ""
"In the regular expression editor, repeated regular expression is created "
"using the <link linkend=\"repeattool\">repeat tool</link>"
msgstr ""

#: index.docbook:241
#, no-c-format
msgid ""
"Replacing <literal>&amp;</literal> with <literal>&amp;amb;</literal>"
" in HTML document"
msgstr ""

#: index.docbook:241
#, no-c-format
msgid ""
"In HTML the special character <literal>&amp;</literal> must be written as "
"<literal>&amp;amp;</literal> - this is similar to escaping in regular "
"expression."
msgstr ""

#: index.docbook:241
#, no-c-format
msgid ""
"Imagine that you have written an HTML document in a normal editor (e.g. "
"XEmacs or Kate), and you totally forgot about this rule. What you would do "
"when realized your mistake was to replace every occurrences of "
"<literal>&amp;</literal> with <literal>&amp;amp;</literal>."
msgstr ""

#: index.docbook:241
#, no-c-format
msgid ""
"This can easily be done using normal search and replace, there is, however, "
"one glitch. Imagine that you did remember this rule - <emphasis>just a "
"bit</emphasis> - and did it right some of the places. Replacing "
"unconditional would result in <literal>&amp;amp;</literal>"
" would be replaced with <literal>&amp;amp;amp;</literal>"
msgstr ""

#: index.docbook:241
#, no-c-format
msgid ""
"What you really want to say is that <literal>&amp;</literal> should only be "
"placed if it is <emphasis>not</emphasis> followed by the letters "
"<literal>amp;</literal>. You can do this using regular expressions using "
"<emphasis>positive lookahead</emphasis>."
msgstr ""

#: index.docbook:241
#, no-c-format
msgid ""
"The regular expression, which only matches an ampersand if it is not "
"followed by the letters <literal>amp;</literal> looks as follows: "
"<literal>&amp;(?!amp;)</literal>. This is, of course, easier to read using "
"the regular expression editor, where you would use the <link "
"linkend=\"lookaheadtools\">lookahead tools</link>."
msgstr ""

#: index.docbook:278
#, no-c-format
msgid "Using the Regular Expresion Editor"
msgstr ""

#: index.docbook:280
#, no-c-format
msgid "This chapter will tell you about how the regular expression editor works."
msgstr ""

#: index.docbook:288
#, no-c-format
msgid "The organization of the screen"
msgstr ""

#: index.docbook:294
#, no-c-format
msgid ""
"The most important part of the editor is of course the editing area, this is "
"the area where you draw your regular expression. This area is the larger "
"gray one in the middle."
msgstr ""

#: index.docbook:298
#, no-c-format
msgid ""
"Above the editing area you have two tool-bars, the first one contains the "
"<link linkend=\"editingtools\">editing actions</link> - much like drawing "
"tools in a drawing program. The second tool bar contains the <emphasis>"
"whats this</emphasis> button, and buttons for undo and redo."
msgstr ""

#: index.docbook:304
#, no-c-format
msgid "<para></para>"
msgstr "<para></para>"

#: index.docbook:306
#, no-c-format
msgid ""
"Below the editing area you find the regular expression currently build, in "
"the so called ascii syntax. The ascii syntax is updated while you edit the "
"regular expression in the graphical editor. If you rather want to update the "
"ascii syntax then please do, the graphical editor is updated on the fly to "
"reflect your changes."
msgstr ""

#: index.docbook:313
#, no-c-format
msgid ""
"Finally to the left of the editor area you will find a number of pre-build "
"regular expressions. They serve two purposes: (1) When you load the editor "
"with a regular expression then this regular expression is made "
"<emphasis>nicer</emphasis>"
" or more comprehensive by replacing common regular expressions. In the "
"screen dump above, you can see how the ascii syntex \".*\" have been "
"replaced with a box saying \"anything\". (2) When you insert regular "
"expression you may find building blocks for your own regular expression from "
"the set of pre build regular expressions. See the section on <link "
"linkend=\"userdefinedregexps\">user defined regular expressions</link> to "
"learn how to save your own regular expressions."
msgstr ""

#: index.docbook:330
#, no-c-format
msgid "Editing Tools"
msgstr ""

#: index.docbook:331
#, no-c-format
msgid ""
"The text in this section expects that you have read the chapter on <link "
"linkend=\"whatIsARegExp\">what a regular expression is</link>, or have "
"previous knowledge on this subject."
msgstr ""

#: index.docbook:335
#, no-c-format
msgid ""
"All the editing tools are located in the tool bar above editing area. Each "
"of them will be described in the following."
msgstr ""

#: index.docbook:341
#, no-c-format
msgid "Selection Tool"
msgstr ""

#: index.docbook:345
#, no-c-format
msgid ""
"The selection tool is used to mark elements for cut-and-paste and "
"drag-and-drop. This is very similar to a selection tool in any drawing "
"program."
msgstr ""

#: index.docbook:352
#, no-c-format
msgid "Text Tool"
msgstr ""

#: index.docbook:360
#, no-c-format
msgid ""
"Using this tool you will insert normal text to match. The text is matched "
"literally, i.e. you do not have to worry about escaping of special "
"characters. In the example above the following regular expression will be "
"build: <literal>abc\\*\\\\\\)</literal>"
msgstr ""

#: index.docbook:368
#, no-c-format
msgid "Character Tool"
msgstr ""

#: index.docbook:376
#, no-c-format
msgid ""
"Using this tool you insert character ranges. Examples includes what in ASCII "
"text says <literal>[0-9]</literal>, <literal>[^a-zA-Z,_]</literal>. When "
"inserting an item with this tool a dialog will apear, in which you specify "
"the character ranges."
msgstr ""

#: index.docbook:382
#, no-c-format
msgid ""
"See description of <link linkend=\"repeatregexp\">repeated regular "
"expressions</link>."
msgstr ""

#: index.docbook:388
#, no-c-format
msgid "Any Character Tool"
msgstr ""

#: index.docbook:395
#, no-c-format
msgid "This is the regular expression \"dot\" (.). It matches any single character."
msgstr ""

#: index.docbook:404
#, no-c-format
msgid "Repeat Tool"
msgstr ""

#: index.docbook:412
#, no-c-format
msgid ""
"This is the repeated elements. This includes what in ASCII syntax is "
"represented using an asterix (*), a plus (+), a question mark (?), and "
"ranges ({3,5}). When you insert an item using this tool, a dialog will "
"appear asking for the number of times to repeat."
msgstr ""

#: index.docbook:419
#, no-c-format
msgid ""
"You specify what to repeat by drawing the repeated content inside the box "
"which this tool inserts."
msgstr ""

#: index.docbook:422
#, no-c-format
msgid ""
"Repeated elements can both be build outside in and inside out. That is you "
"can first draw what to be repeated, select it and use the repeat tool to "
"repeat it. Alternatively you can first insert the repeat element, and draw "
"what to be repeated inside it."
msgstr ""

#: index.docbook:428
#, no-c-format
msgid ""
"See description on the <link linkend=\"repeatregexp\">repeated regular "
"expressions</link>."
msgstr ""

#: index.docbook:435
#, no-c-format
msgid "Alternative Tool"
msgstr ""

#: index.docbook:442
#, no-c-format
msgid ""
"This is the alternative regular expression (|). You specify the alternatives "
"by drawing each alternative on top of each other inside the box that this "
"tool inserts."
msgstr ""

#: index.docbook:446
#, no-c-format
msgid ""
"See description on <link linkend=\"altnregexp\">alternative regular "
"expressions</link>"
msgstr ""

#: index.docbook:453
#, no-c-format
msgid "Compound Tool"
msgstr ""

#: index.docbook:460
#, no-c-format
msgid ""
"The compound tool does not represent any regular expressions. It is used to "
"group other sub parts together in a box, which easily can be collapsed to "
"only its title. This can be seen in the right part of the screen dump above."
msgstr ""

#: index.docbook:470
#, no-c-format
msgid ""
"Line Start/End Tools <inlinemediaobject><imageobject> <imagedata "
"format=\"PNG\" fileref=\"begline.png\"/> "
"</imageobject></inlinemediaobject>&nbsp;&nbsp;"
msgstr ""

#: index.docbook:480
#, no-c-format
msgid ""
"The line start and line end tools matches the start of the line, and the end "
"of the line respectively. The regular expression in the screen dump above "
"thus matches lines only matches spaces."
msgstr ""

#: index.docbook:485
#, no-c-format
msgid ""
"See description of <link linkend=\"positionregexp\">position regular "
"expressions</link>."
msgstr ""

#: index.docbook:493
#, no-c-format
msgid ""
"Word (Non)Boundary Tools <inlinemediaobject><imageobject> <imagedata "
"format=\"PNG\" fileref=\"wordboundary.png\"/> "
"</imageobject></inlinemediaobject>&nbsp;&nbsp;"
msgstr ""

#: index.docbook:502
#, no-c-format
msgid ""
"The boundary tools matches a word boundary respectively a non-word boundary. "
"The regular expression in the screen dump thus matches any words starting "
"with <literal>the</literal>. The word <literal>the</literal> itself is, "
"however, not matched."
msgstr ""

#: index.docbook:507
#, no-c-format
msgid ""
"See description of <link linkend=\"boundaryregexp\">boundary regular "
"expressions</link>."
msgstr ""

#: index.docbook:515
#, no-c-format
msgid ""
"Positive/Negative Lookahead Tools <inlinemediaobject><imageobject> "
"<imagedata format=\"PNG\" fileref=\"poslookahead.png\"/> "
"</imageobject></inlinemediaobject>&nbsp;&nbsp;"
msgstr ""

#: index.docbook:525
#, no-c-format
msgid ""
"The look ahead tools either specify a positive or negative regular "
"expression to match. The match is, however, not part of the total match."
msgstr ""

#: index.docbook:529
#, no-c-format
msgid ""
"Note: You are only allowed to place look ahead's at the end of the regular "
"expressions. The Regular Expression Editor widget does not enforce this."
msgstr ""

#: index.docbook:533
#, no-c-format
msgid ""
"See description of <link linkend=\"lookaheadregexp\">look ahead regular "
"expressions</link>."
msgstr ""

#: index.docbook:542
#, no-c-format
msgid "User Defined Regular Expressions"
msgstr ""

#: index.docbook:543
#, no-c-format
msgid ""
"To the left of the editing area is a list box located containing user "
"defined regular expressions. Some regular expressions are pre installed with "
"your KDE installation, while other you can save yourself."
msgstr ""

#: index.docbook:548
#, no-c-format
msgid ""
"These regular expression serves two purposes ( <link "
"linkend=\"screenorganization\">see detailed description</link>), namely (1) "
"to offer you a set of building block and (2) to make common regular "
"expressions prettier."
msgstr ""

#: index.docbook:553
#, no-c-format
msgid ""
"You can save your own regular expressions by right clicking the mouse button "
"in the editing area, and choosing <literal>Save Regular Expression</literal>."
msgstr ""

#: index.docbook:557
#, no-c-format
msgid ""
"If the regular expression you save is within a <link "
"linkend=\"compoundtool\">compound container</link> then the regular "
"expression will take part in making subsequent regular expressions pretier."
msgstr ""

#: index.docbook:562
#, no-c-format
msgid ""
"User defined regular expression can be deleted or renamed by pressing the "
"right mouse button on top of the regular expression in question in the list "
"box."
msgstr ""

#: index.docbook:572
#, no-c-format
msgid "Reporting bugs and Suggesting Features"
msgstr ""

#: index.docbook:573
#, no-c-format
msgid ""
"Bugs reported and features are reported through the <ulink "
"url=\"http://bugs.kde.org/\">KDE Bug Tracking System</ulink>. <emphasis "
"role=\"strong\">Before</emphasis> you report a bug or suggest a feature, "
"please check that it hasn't already been <ulink "
"url=\"http://bugs.kde.org/db/pa/lkregexpeditor.html\">"
"reported/suggested</ulink>"
msgstr ""

#: index.docbook:584
#, no-c-format
msgid "Frequently Asked Questions"
msgstr ""

#: index.docbook:586
#, no-c-format
msgid "Does the regular expression editor support back references"
msgstr ""

#: index.docbook:587
#, no-c-format
msgid "No currently this is not supported. It is planned for the next version."
msgstr ""

#: index.docbook:592
#, no-c-format
msgid "Does the regular expression editor support showing matches"
msgstr ""

#: index.docbook:593
#, no-c-format
msgid "No, hopefully this will be available in the next version"
msgstr ""

#: index.docbook:597
#, no-c-format
msgid "I'm the author of a KDE program, how can I use this widget in my application."
msgstr ""

#: index.docbook:599
#, no-c-format
msgid ""
"see <ulink "
"url=\"http://developer.kde.org/documentation/library/cvs-api/classref/interfa"
"ces/KRegExpEditorInterface.html\">The documentation for the class "
"KRegExpEditorInterface</ulink>"
msgstr ""

#: index.docbook:604
#, no-c-format
msgid ""
"I can't find the <emphasis>Edit Regular expression</emphasis> button in for "
"example konqueror on another KDE3 installation, why?"
msgstr ""

#: index.docbook:606
#, no-c-format
msgid ""
"The regular expression widget is located in the package KDE-utils. If you do "
"not have this package installed, then the <emphasis>edit regular "
"expressions</emphasis> buttons will not appear in the programs."
msgstr ""

#: index.docbook:617
#, no-c-format
msgid "Credits and Licenses"
msgstr "Amatyala Nelayisenisi"

#: index.docbook:619
#, no-c-format
msgid ""
"Documentation is copyright 2001, Jesper K. Pedersen "
"<email>blackie@kde.org</email>"
msgstr ""
