# translation of khelpcenter_userguide_ug-faq.po to 
# translation of khelpcenter_userguide_ug-faq.po to
# translation of khelpcenter_userguide_ug-faq.po to
# Copyright (C) 2002 Free Software Foundation, Inc.
# Lwandle Mgidlana <lwandle@translate.org.za>, 2002
#
msgid ""
msgstr ""
"Project-Id-Version: khelpcenter_userguide_ug-faq\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: 2002-09-26 12:31+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 "Frequently Asked Questions About &kde;"
msgstr ""

#: index.docbook:6
#, no-c-format
msgid "What are you?"
msgstr "Uphi?"

#: index.docbook:7
#, no-c-format
msgid "I'm your worst nightmare..."
msgstr "Ndilelona phupha lakho libi kakhului..."

#: index.docbook:10
#, no-c-format
msgid ""
"There are some questions that are always raised on the &kde; mailing lists. "
"To keep the traffic as low as possible (making the lists more readable), we "
"have included them in this section. So please be kind and do not ask them in "
"the mailing lists anymore - think of the quote above!"
msgstr ""

#: index.docbook:21
#, no-c-format
msgid "What does <quote>&kde;</quote> stand for?"
msgstr ""

#: index.docbook:22
#, no-c-format
msgid ""
"&kde; stands for the <emphasis>K Desktop Environment</emphasis>"
" which itself is intended to be a collection of small tools, a window "
"manager, a file manager and tools that bring all this together. It is "
"created to make your life with &UNIX; easier."
msgstr ""

#: index.docbook:30
#, no-c-format
msgid "I cannot compile package xxx"
msgstr "Andinakuqokelela impahla xxx"

#: index.docbook:33
#, no-c-format
msgid ""
"Always be sure that you have the newest version of the &kde; libraries "
"installed. The software is in constant development, so the dependencies can "
"change from one day to another if you are using <acronym>CVS</acronym>. For "
"most users, using a released version is much more practical."
msgstr ""

#: index.docbook:39
#, no-c-format
msgid ""
"You may also find the <link linkend=\"source-distribution\">general "
"compilation hints</link> helpful. Another problem could be that you are "
"using a program written for a very old version of &kde;, which depends on "
"outdated include files. Check in the source archive's "
"<filename>README</filename>"
" to see if it explains which version of &kde; the application is looking "
"for. If that file doesn't exist, check the file dates. They should be more "
"recent than your current &kde; version."
msgstr ""

#: index.docbook:52
#, no-c-format
msgid "What version of &kde; should I use for a stable desktop?"
msgstr ""

#: index.docbook:54
#, no-c-format
msgid ""
"One can, in general, obtain &kde; in many ways. Obtaining pre-compiled "
"binaries in a package format (rpm,deb,tgz) labeled with a particular version "
"(&eg; 3.0) is the best way to encourage stability on your &kde; desktop."
msgstr ""

#: index.docbook:63
#, no-c-format
msgid ""
"But I heard that my problem/wishlist item is <quote>already in "
"<acronym>CVS</acronym></quote>. I want to get my hands on the new features, "
"why shouldn't I try <acronym>CVS</acronym>?"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"The price of stability is that one must wait for each release to get new "
"features. Conversely the price of being the first to see new features, is "
"that you risk stability. &kde; has a fairly frequent release schedule, and "
"stability of released versions is a particular focus. For the majority of "
"&kde; users, unless you are planning to help develop &kde;, there is little "
"advantage to running development versions of &kde;."
msgstr ""

#: index.docbook:77
#, no-c-format
msgid ""
"However, there is always a place for experienced users who know what they "
"are letting themselves in for, and are willing to report bugs found. If this "
"is you, then there is no reason not to try the <acronym>CVS</acronym> "
"versions. Be prepared for things to break occasionally, "
"<acronym>CVS</acronym>"
" gives you a snapshot of source code that is currently being worked on."
msgstr ""

#: index.docbook:84
#, no-c-format
msgid ""
"These are daily snapshots of whatever the developers are working on, and "
"some things are guaranteed to be broken."
msgstr ""

#: index.docbook:88
#, no-c-format
msgid ""
"<emphasis>Do not rely on <acronym>CVS</acronym> snapshots to maintain "
"operational desktops</emphasis>. You will get burned eventually!"
msgstr ""
