faq.docbook.pot

LINUX 下, 以 QT/KDE 写的档案管理员

# Translation of faq.docbook to LANGUAGE
# Copyright (C) 2006, Krusader Krew
# This file is distributed under the same license as the Krusader package
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krusader-doc-1.90.0 2008-03-14\n"
"Report-Msgid-Bugs-To:  <[e-mail]>\n"
"POT-Creation-Date: 2008-03-14 18:22+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <[e-mail]>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#: faq.docbook:22
#, no-c-format
msgid "Frequently Asked Questions (&FAQ;)"
msgstr ""

#. Tag: primary
#: faq.docbook:24
#, no-c-format
msgid "<primary>FAQ</primary>"
msgstr ""

#. Tag: para
#: faq.docbook:28
#, no-c-format
msgid "If you have problems with &krusader; please check the &install-proc-lnk;, as your problem may be caused by a bad installation."
msgstr ""

#. Tag: para
#: faq.docbook:31
#, no-c-format
msgid "The &FAQ; is divided into three sections: <itemizedlist> <listitem> <para> <link linkend=\"faq_installation\">Installation &FAQ;</link> (this page)</para> </listitem> <listitem> <para> <link linkend=\"faq_usage\">Usage &FAQ;</link> (issues with running/using &krusader;)</para> </listitem> <listitem> <para> <link linkend=\"faq_general\">General &FAQ;</link> (bug reports, forum, mailing list, ...)</para> </listitem> </itemizedlist>If you feel that a &FAQ; is missing or if something is not clear to you, please <link linkend=\"editors_note\">let us know</link>."
msgstr ""

#. Tag: title
#: faq.docbook:54
#, no-c-format
msgid "Installation &FAQ;"
msgstr ""

#. Tag: para
#: faq.docbook:58
#, no-c-format
msgid "Does &krusader; need &kde; to run?"
msgstr ""

#. Tag: para
#: faq.docbook:62
#, no-c-format
msgid "<emphasis>No, &krusader; does not need the &kde; window manager</emphasis> to run on your computer but &krusader;'s natural environment is &kde;, because it relies on services provided by the &kde; base libraries. Only some shared libraries are needed &eg; &kde; libraries, &Qt; libraries, &etc; This means that &krusader; runs on &gnome-url;, &afterstep-url;, &xfce-url; and other window managers provided the approriate libraries are installed on your computer. All this is not a problem since the apt-get world can resolve these dependencies instantly."
msgstr ""

#. Tag: para
#: faq.docbook:79
#, no-c-format
msgid "You do not need to switch to the &kde; window manager to use &krusader;; you can still use &gnome-url;, &afterstep-url;, &xfce-url; or another window manager. However, the configuration of the &krusader; fonts and some behavior is done by running <command>kcontrol</command>."
msgstr ""

#. Tag: para
#: faq.docbook:89
#, no-c-format
msgid "A lot depends on what you want to do with &krusader;. You should know that &krusader; uses the &kde; &kioslaves1-url; to access remote file systems, and support for only a limited number of file system types are shipped with &kdelibs-url;, most of the &kioslaves2-url; are bundled with &kdebase-url; (including fish, sftp and tar). However, if you want the property-dialog to show EXIF-data for .jpeg's, you need &kde;graphics. If you want ID3-infos, you need &kde;multimedia, and so on."
msgstr ""

#. Tag: para
#: faq.docbook:103
#, no-c-format
msgid "To summarize, if you want a working &krusader; - install &kde;libs. If you want a functional &krusader; then you need &kde;libs + &kde;base. For maximum functionality, &krusader; needs all of the &kde; package libraries, but the &kde; window manager is optional."
msgstr ""

#. Tag: para
#: faq.docbook:116
#, no-c-format
msgid "Which libraries does &krusader; need to run?"
msgstr ""

#. Tag: para
#: faq.docbook:120
#, no-c-format
msgid "For running &krusader; (&eg; when you have installed &krusader; with a binary RPM) you need less libraries than if you compile &krusader; from source. &eg; you only need the C-compliler &gcc; when you compile &krusader; from source (see the next question)."
msgstr ""

#. Tag: para
#: faq.docbook:127
#, no-c-format
msgid "Here is a list of the required shared libraries when you run &krusader;:"
msgstr ""

#. Tag: para
#: faq.docbook:132
#, no-c-format
msgid "kdelibs (for the required &kde; version see the &install-proc-lnk;)"
msgstr ""

#. Tag: para
#: faq.docbook:136
#, no-c-format
msgid "libacl1 libart-2.0 libattr1 libaudio2 libc6 libfam0 libfontconfig1"
msgstr ""

#. Tag: para
#: faq.docbook:140
#, no-c-format
msgid "libfreetype6 libgcc1 libgcc2 libice6 libidn11 libjpeg62 libkjsembed1"
msgstr ""

#. Tag: para
#: faq.docbook:144
#, no-c-format
msgid "libkonq4 libpcre3 libpng12 libqt3-mt libsm6 libstdc++6 libunwind7 libx11-6"
msgstr ""

#. Tag: para
#: faq.docbook:148
#, no-c-format
msgid "libxcursor1 libxext6 libxft2 libxi6 libxinerama1 libxrandr2 libxrender1 libxt6 zlib1g"
msgstr ""

#. Tag: para
#: faq.docbook:152
#, no-c-format
msgid "If you need more info please take a look at the &deb-requirements-url; ."
msgstr ""

#. Tag: para
#: faq.docbook:160
#, no-c-format
msgid "I have followed all the steps but <command>configure</command>complains about missing libs or headers. What do I need to do?"
msgstr ""

#. Tag: para
#: faq.docbook:165
#, no-c-format
msgid "Install the missing packages."
msgstr ""

#. Tag: para
#: faq.docbook:166
#, no-c-format
msgid "Here is a list of the required packages to compile &krusader; from source:"
msgstr ""

#. Tag: para
#: faq.docbook:171
#, no-c-format
msgid "gcc-cpp gcc-c++ glibc libgcc1 (other compilers may work but haven't been tested)"
msgstr ""

#. Tag: para
#: faq.docbook:175
#, no-c-format
msgid "autoconf automake XFree"
msgstr ""

#. Tag: para
#: faq.docbook:178
#, no-c-format
msgid "libqt3 libqt-devel"
msgstr ""

#. Tag: para
#: faq.docbook:181
#, no-c-format
msgid "kdelibs kdelibs-devel"
msgstr ""

#. Tag: para
#: faq.docbook:184
#, no-c-format
msgid "libjpeg62 libjpeg-devel libpng3 libmng1"
msgstr ""

#. Tag: para
#: faq.docbook:188
#, no-c-format
msgid "fam libfam-devel"
msgstr ""

#. Tag: para
#: faq.docbook:191
#, no-c-format
msgid "zlib1 arts libart_lgpl2 libstdc++5 libpcre0"
msgstr ""

#. Tag: para
#: faq.docbook:195
#, no-c-format
msgid "libkjsembed, if you use the &javascript-console-lnk;, often found in a package called KDEbindings(-devel) and libkonq-dev for the &konqueror; right-click menu entries."
msgstr ""

#. Tag: para
#: faq.docbook:203
#, no-c-format
msgid "Most RPM-based distributions separate the headers from the libs. The headers are needed to compile &krusader;. Look for packages in the form foo-devel-*.rpm (&eg; <filename>kdelibs-devel-foo.i586.rpm</filename>) or foo-dev-*.deb for &debian; based distributions. These are usually included with your distribution."
msgstr ""

#. Tag: para
#: faq.docbook:212
#, no-c-format
msgid "If you ca not find the needed package, use &rpmfind-url; and click 'missing lib or header' in the search line. Or use <command>apt-cache search <replaceable>foo</replaceable></command> to find the corresponding package for &debian; based distributions."
msgstr ""

#. Tag: para
#: faq.docbook:226
#, no-c-format
msgid "How do I compile &krusader; when I'm using a 64 bit processor ?"
msgstr ""

#. Tag: para
#: faq.docbook:230
#, no-c-format
msgid "As far as we know, there are no issues. &krusader; is also available on <ulink url=\"http://packages.debian.org/unstable/utils/krusader\"> many other architectures</ulink>."
msgstr ""

#. Tag: para
#: faq.docbook:240
#, no-c-format
msgid "I have downloaded the Source RPM <filename>krusader-x.xx.dist.src.rpm</filename>, what to do now?"
msgstr ""

#. Tag: para
#: faq.docbook:248 faq.docbook:664
#, no-c-format
msgid "Check the ownership and the permissions on <filename class=\"directory\"> /usr/src/RPM/</filename> and all recursive directories that your normal user can read-write-execute in these directories."
msgstr ""

#. Tag: para
#: faq.docbook:255
#, no-c-format
msgid "To produce the binary RPM for your computer, do this:"
msgstr ""

#. Tag: screen
#: faq.docbook:257
#, no-c-format
msgid "<prompt>$</prompt> <userinput><command>rpm</command> <option>--rebuild</option> <replaceable>&lt;/path/to/rpmfile/&gt; krusader-x.xx.dist.src.rpm</replaceable></userinput>"
msgstr ""

#. Tag: para
#: faq.docbook:261
#, no-c-format
msgid "If all <link linkend=\"faqi_missing_libs\"> dependencies</link> are OK, a binary RPM <filename>krusader-x.xx.dist.rpm</filename> will be created at <filename class=\"directory\"> /usr/src/RPM/RPMS/i586</filename> (replace i586 with your architecture)."
msgstr ""

#. Tag: para
#: faq.docbook:271
#, no-c-format
msgid "Test the binary RPM for errors before installing: <screen><prompt>$</prompt> <userinput><command>rpm</command> <option>-i --test</option> <replaceable>&lt;/path/to/rpmfile&gt; krusader-x.xx.dist.rpm</replaceable></userinput></screen> If the prompt returns without any message, then everything is OK."