faq.docbook.pot

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

msgstr ""

#. Tag: para
#: faq.docbook:278
#, no-c-format
msgid "Install the binary RPM as usual, for example: <screen><prompt>$</prompt> <userinput><command>su -c 'rpm</command> <option>-Uvh</option> <replaceable>&lt;/path/to/rpmfile&gt; krusader-x.xx.dist.rpm</replaceable>'</userinput></screen> You will be asked to enter your root password."
msgstr ""

#. Tag: para
#: faq.docbook:284
#, no-c-format
msgid "Now you can <link linkend=\"starting-krusader\"> start</link> &krusader;."
msgstr ""

#. Tag: para
#: faq.docbook:293
#, no-c-format
msgid "For more information about RPM, visit &rpm-org-url; and read the &rpm-guide-url; by Eric Foster-Johnson."
msgstr ""

#. Tag: para
#: faq.docbook:304
#, no-c-format
msgid "I'm trying to install binary foo (RPM or DEB package), but it fails. What's wrong?"
msgstr ""

#. Tag: para
#: faq.docbook:308
#, no-c-format
msgid "Since we only prepare (and use) the source, we have no way of knowing this. Did you test the binary RPM 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. RPM's downloaded from our website are usually provided by &krusader; users. Visit your distro website and search for an updated RPM."
msgstr ""

#. Tag: para
#: faq.docbook:316
#, no-c-format
msgid "If the RPM is not OK, try to find another package at &Linux; software archives such as &freshmeat-url; or &kde-apps-url;. If you still can't find the appropriate package for your &Linux; distribution, we recommend searching for it with &rpmfind-url; or &rpmpbone-url;."
msgstr ""

#. Tag: para
#: faq.docbook:323
#, no-c-format
msgid "In general, a package for an older version of your distrubution or even for another distribution might work on your computer (&eg; FC RPM's often work on Mdk and RH, and vice versa), but it is always the best that you install only RPM's that exactly match your distribution. If you can't find a package that matches your distribution version, architecture or distribution, then use a source RPM. When you use a source RPM, the Krusader sources will be built, on your computer, guaranteeing a suitable binary RPM for your specific distribution and architecture. In addition, this method results in maximum system speed, since the resulting binary is customized for your computer. Please read the previous question, it explains how to install a source RPM. The best solution is explained in the next question."
msgstr ""

#. Tag: para
#: faq.docbook:345
#, no-c-format
msgid "I can't find an RPM or DEB package for &krusader;, what to do?"
msgstr ""

#. Tag: para
#: faq.docbook:349
#, no-c-format
msgid "Check if your distribution provides &krusader;, if it doesn't then contact your distribution creator and ask them to include &krusader;!"
msgstr ""

#. Tag: para
#: faq.docbook:353
#, no-c-format
msgid "Did you take a look at the &URL;'s on the &install-proc-lnk; page? If you have and found nothing, you can always compile &krusader; from source. Even if you feel you haven't got the necessary skills, you will probably succeed in compiling &krusader;: we provide a very detailed installation procedure. This HowTo enables newcomers to compile &krusader; from source, even if they have never done a compilation from source before, just follow the instructions carefully. Feel free to post a &help-request-lnk; if you encounter problems."
msgstr ""

#. Tag: para
#: faq.docbook:371
#, no-c-format
msgid "I've installed &krusader;, but when I start, only the <guimenu>\"Help\"</guimenu> menu appears. Why?"
msgstr ""

#. Tag: para
#: faq.docbook:376
#, no-c-format
msgid "In this case only the <guimenu>Help</guimenu> menu is visible and all other menu items like &eg; <guimenu>File</guimenu> and <guimenu>Select</guimenu> are missing. This is because some distributions put the <filename>krusaderui.rc</filename> file in the wrong directory. To solve the problem, just copy the <filename>krusaderui.rc</filename> file from the package <filename> krusader_kde3/krusader/krusaderui.rc</filename> to <filename> $KDEDIR/share/apps/krusader/krusaderui.rc</filename> and <filename> ~/.kde/share/apps/krusader/krusaderui.rc</filename> and re-run &krusader;. If you have compiled &krusader; from sources this is often caused if the &kdeqtdir-lnk; environment variables are not correctly set. The result is that the <filename>krusaderui.rc</filename> file is installed in the wrong directory. Please read the following question, as well."
msgstr ""

#. Tag: para
#: faq.docbook:404
#, no-c-format
msgid "Some new menu items are missing after updating &krusader;, what's wrong?"
msgstr ""

#. Tag: para
#: faq.docbook:408
#, no-c-format
msgid "The <filename>krusaderui.rc</filename> file is stored in <filename> $KDEDIR/share/apps/krusader/krusaderui.rc</filename>. When you change the <guilabel>\"Toolbar\"</guilabel>, &kde; makes a copy of that file in the home directory at <filename> ~/.kde/share/apps/krusader/krusaderui.rc</filename>. If Krusader was previously installed on your computer, and you install a newer &krusader; version the <filename> ~/.kde/share/apps/krusader/krusaderui.rc</filename> file must be replaced with the newer version. Note: this will also reset all your changes on toolbars and shortcuts!"
msgstr ""

#. Tag: para
#: faq.docbook:424
#, no-c-format
msgid "The first line of <filename>krusaderui.rc</filename> contains the version number. After installing a newer &krusader; version, &kde; will automatically replace the old <filename> ~/.kde/share/apps/krusader/krusaderui.rc</filename> with the newer version when starting the new &krusader; for the first time (&kde; will detect the newer version number in the first line)."
msgstr ""

#. Tag: para
#: faq.docbook:435
#, no-c-format
msgid "If you install a CVS or beta version and &krusader; was already installed on your computer then you should delete the <filename>krusaderui.rc</filename> file from your home directory to activate the new menu entries <prompt>$</prompt> <userinput> <command>rm</command> <option> ~/.kde/share/apps/krusader/krusaderui.rc</option> </userinput>"
msgstr ""

#. Tag: para
#: faq.docbook:446
#, no-c-format
msgid "If the <filename> ~/.kde/share/apps/krusader/krusaderui.rc</filename> file is older, then the new menu elements will not be shown. Read the previous question for information on how to update the <filename>krusaderui.rc</filename> file. If <filename>krusaderui.rc</filename> is missing or in a wrong directory, only the <guimenu>\"Help\"</guimenu> menu appears, please read the previous question."
msgstr ""

#. Tag: para
#: faq.docbook:463
#, no-c-format
msgid "When I run <command>make</command>, it complains about <filename>libfam.la</filename>, what's wrong?"
msgstr ""

#. Tag: para
#: faq.docbook:468
#, no-c-format
msgid "The <command>./configure</command> script does not check for the presence of <filename>libfam.la</filename>, and <command>make</command> needs <filename>libfam.la</filename> to compile &krusader;. If you know how this can be solved, please let us know. Install <filename>libfam0-devel-foo.rpm</filename>. Note: when you install &Mandrake;-&Linux; 9.2 with the default settings, this package is not installed. If you need more information take a look at &missing-libs-lnk;."
msgstr ""

#. Tag: para
#: faq.docbook:487
#, no-c-format
msgid "&debian; complains about &Qt; when running <command>./configure</command>, what's wrong?"
msgstr ""

#. Tag: para
#: faq.docbook:492
#, no-c-format
msgid ""
      "This problem occurs when you use &gcc; 2.95, you need to install &gcc; 3.2 (or higher). You also need to set the enviroment variables \"CC, CPP and CXX\" before running the <command>./configure</command> script. <screen><prompt>$</prompt> <userinput><command>export</command> CC=<replaceable>/usr/bin/gcc-3.2</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>export</command> CXX=<replaceable>/usr/bin/g++-3.2</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>export</command> CPP=<replaceable>/usr/bin/cpp-3.2</replaceable></userinput>
\n"
      "          </screen> For more information please take a look &debian-qt-a-url; and at the &debian-qt-b-url; on how to build a &Qt;/&kde;3 application on &debian;."
msgstr ""

#. Tag: para
#: faq.docbook:512
#, no-c-format
msgid "I have a <filename>libGLcore.so.1</filename> compile error after using the &nvidia; installer, what to do?"
msgstr ""

#. Tag: para
#: faq.docbook:518
#, no-c-format
msgid "This problem occurs when you use the &nvidia; installer and not the official &nvidia; packages of your distribution. &krusader; is based on &Qt; which can be linked against the X OpenGL libraries. As a result &krusader; may look for OpenGL as well. The problem is that the &nvidia; installer (prior to version 7xxx) doesn't perform it's task properly: it replaces the OpenGL header files (which get included into &krusader;) but doesn't set the libGL links correctly. The best solution is to use the &nvidia; packages provided by your distributor or a new &nvidia; installer, the current version at the moment of writing is 7114. If, for some reason, you must use an old &nvidia; driver, one solution is the following hack, the exact commands depend on the distribution used and the version of the &nvidia; driver (6111 in this example), but it should read something like this:"
msgstr ""

#. Tag: screen
#: faq.docbook:537
#, no-c-format
msgid ""
      "<prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGLcore.so.0</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGLcore.so</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGLcore.so.1.0.0</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGLcore.so.0.0.0</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGL.so</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGL.so.0</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGL.so.0.0.0</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGL.so.1</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>libGLcore.so.1.0.6111 libGL.so.1.0.0</replaceable></userinput>
\n"
      "          <prompt>$</prompt> <userinput><command>ln</command> -s <replaceable>/usr/lib/libGLU.la /usr/X11R6/lib/libGLU.la</replaceable></userinput>"
msgstr ""

#. Tag: para
#: faq.docbook:554
#, no-c-format
msgid "Why &krusader;-1.60.x does not compile with gcc4?"
msgstr ""

#. Tag: para
#: faq.docbook:558
#, no-c-format
msgid "Because &krusader;-1.60.x was not gcc4 compatible, it first needs some patches: <itemizedlist> <listitem> <para>add 'class ListPanelFunc;' in krusader/Panel/listpanel.h</para> </listitem> <listitem> <para>add 'class KMountManGUI;' in krusader/MountMan/kmountman.h</para> </listitem> <listitem> <para>add 'class KrDetailedViewItem;' in krusader/Panel/krdetailedview.h</para> </listitem> </itemizedlist>More information can be found in our <ulink url=\"http://www.krusader.org/phpBB/viewtopic.php?t=1328\"> forum</ulink>."
msgstr ""

#. Tag: para
#: faq.docbook:582
#, no-c-format
msgid "I am having trouble compiling and installing &krusader;, how do I send a help request?"
msgstr ""

#. Tag: para
#: faq.docbook:587
#, no-c-format
msgid "Please read our detailed <link linkend=\"compilation\">installation procedure</link> and the &faq-lnk;. If you can't find a solution to your problem then feel free to post a <emphasis role=\"bold\">help request</emphasis> at our &krusader; forum or use the &kruusers-url; mailing list. But before posting a help request, please try the following:"
msgstr ""

#. Tag: para
#: faq.docbook:598
#, no-c-format
msgid "Use the &kruforumsearch-url; function on the &forum-lnk;, your problem might be solved or discussed already."
msgstr ""

#. Tag: para
#: faq.docbook:603
#, no-c-format
msgid "If you can't find a solution, please make a note of the following issues: <itemizedlist> <listitem> <para>the &krusader; version used</para> </listitem> <listitem> <para>the &Linux; distribution + version used</para> </listitem> <listitem> <para>a good description of the problem</para> </listitem> </itemizedlist>Without this information, it is very difficult for us to help you."
msgstr ""

#. Tag: para
#: faq.docbook:620
#, no-c-format
msgid "If you give us the error messages (&eg; <command>make</command> error messages) please start with the FIRST error message, all the error messages which follow the first error message are consequences and not the cause of your problem."
msgstr ""

#. Tag: para
#: faq.docbook:630
#, no-c-format
msgid "Send out your help request."
msgstr ""

#. Tag: para
#: faq.docbook:633 faq.docbook:1475 faq.docbook:1727
#, no-c-format
msgid "Thank you for your co-operation!"
msgstr ""

#. Tag: para
#: faq.docbook:640
#, no-c-format
msgid "How can I build an RPM package for &krusader;?"
msgstr ""

#. Tag: para
#: faq.docbook:644
#, no-c-format
msgid "If you have experience with compiling from source, you will probably be able to build a &krusader; RPM too. Information about RPM can be found at &rpm-org-url; and in the &rpm-guide-url; by Eric Foster-Johnson. The following is the short procedure howto on building an RPM."
msgstr ""

#. Tag: para
#: faq.docbook:652
#, no-c-format
msgid "NEVER build RPMs when logged in as root. Mistakes in building packages (&eg; a bad <filename>krusader.spec</filename> file) can do serious damage to your system when logged in as root."
msgstr ""

#. Tag: para
#: faq.docbook:660
#, no-c-format
msgid "Compile &krusader; from source to check that the compilation works fine."
msgstr ""

#. Tag: para
#: faq.docbook:671
#, no-c-format
msgid "Copy <filename>kusader-1.xx.tar.gz</filename> to <filename class=\"directory\"> /usr/scr/RPM/SOURCE</filename>"
msgstr ""

#. Tag: para
#: faq.docbook:677
#, no-c-format
msgid "Copy <filename>kusader.spec</filename> to <filename class=\"directory\"> /usr/scr/RPM/SPECS</filename> Tip: the latest <filename>kusader.spec</filename> can be found in CVS."
msgstr ""

#. Tag: para
#: faq.docbook:685
#, no-c-format
msgid "Edit <filename>kusader.spec</filename> and add your name, your e-mail address, the rpm name, ... Other changes may be needed if <command>rpmbuild</command> fails."
msgstr ""