faq.docbook.pot

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

#. Tag: para
#: faq.docbook:692
#, no-c-format
msgid "Build the binary and the source RPM with: <screen><prompt>$</prompt> <userinput><command>rpmbuild</command> <option>-ba</option> <replaceable>/usr/scr/RPM/SPECS/krusader.spec</replaceable></userinput></screen> If everything went OK you will have a binary RPM in <filename class=\"directory\"> /usr/src/RPM/RPMS/i586</filename> (depending on your architecture) and a source RPM in <filename class=\"directory\"> /usr/src/RPM/SRPMS/</filename> &eg; <filename> krusader-1.70-beta1.suse10.i586.rpm</filename> and <filename> krusader-1.70-beta1.suse10.src.rpm</filename>"
msgstr ""

#. Tag: para
#: faq.docbook:707
#, no-c-format
msgid "If the build is not OK you will receive an error message during the rpmbuild process, try to fix it and run <command>rpmbuild</command> again."
msgstr ""

#. Tag: para
#: faq.docbook:713
#, no-c-format
msgid "And finally: <link linkend=\"faqi_rpm-source\">test</link> the RPM before sending it in."
msgstr ""

#. Tag: para
#: faq.docbook:725
#, no-c-format
msgid "Why does &krusader;-cvs show an old version number in the about box?"
msgstr ""

#. Tag: para
#: faq.docbook:729
#, no-c-format
msgid "Because we only change the version number just before we do a new release. &krusader;-cvs will show an older version number, so ignore the version number and check the download date. We simply haven't yet decided what the next version number will be."
msgstr ""

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

#. Tag: para
#: faq.docbook:745
#, no-c-format
msgid "&krusader; keeps crashing, why?"
msgstr ""

#. Tag: para
#: faq.docbook:748
#, no-c-format
msgid "We've been receiving a lot of emails and bug reports (December 2005) regarding random crashes, especially during file operations such as copy, move, etc. <emphasis role=\"bold\">These crashes are related to &Qt; 3.3.5 and NOT &krusader;.</emphasis> It seems that &Qt; 3.3.5 introduced a serious bug which is currently (December 2005) causing random crashes in many &kde; applications including &konqueror;. You can use Google to find out more. As far as we know, &debian;-Sid and &SuSE; already posted new &Qt; binaries that fix the problem, and &gentoo; has masked &Qt; 3.3.5 completely. As for now, you either need &Qt; 3.3.4 or a fixed &Qt; 3.3.5 or a higer version, depending on your distribution. More information is available on our <ulink url=\"http://krusader.sourceforge.net/phpBB/viewtopic.php?t=1407\"> website</ulink>."
msgstr ""

#. Tag: para
#: faq.docbook:774
#, no-c-format
msgid "When I try to mount/unmount my cdrom/floppy, &krusader; reports something about a supermount, what's this about?"
msgstr ""

#. Tag: para
#: faq.docbook:779
#, no-c-format
msgid "Supermount is a daemon which handles the mounting/unmounting of removable filesystems for you. Just insert a floppy, and do <userinput> <command>cd</command> <option> <replaceable>/mnt/floppy</replaceable> </option> </userinput>supermount will do the mount for you automatically and transparently. Usually this works fine. However, supermount misleads the system into thinking that the <hardware>floppy/cdrom</hardware> is mounted at all times! This creates some problems for &krusader;, as it cannot really know when the floppy or CD has been removed because the system information is not correctly updated by supermount - is there really a <hardware>floppy</hardware> in the <hardware>drive</hardware>? Of course, this can be solved, but as for now, we don't consider it a priority."
msgstr ""

#. Tag: para
#: faq.docbook:806
#, no-c-format
msgid "Why does &krusader; freeze or hang on a dead mountpoint?"
msgstr ""

#. Tag: para
#: faq.docbook:810
#, no-c-format
msgid "When &krusader; is &eg; browsing an NFS share and the NFS server goes down, &krusader; will freeze. This &krusader; (and all other open internal viewers/editors) freeze is fatal, and can only be corrected with the <command>kill -9</command>. We have no solution for this. This is an issue not confined to file managers, or even the &Linux; OS! The problem is that you \"hang\" on the first access to the dead share - so there is no way around it, no check to avoid it, even <command>ls</command> will freeze. Just trying to read something - anything - is enough to get you stuck. The one and only way around this architectural problem is using a multi-threaded design - this way if we get stuck, we don't hang the entire application event loop, but we don't think that the time is right for adding threads, we are not sure that *all* the &kde; systems out there are using &Qt;-mt (the multi threaded version of the &Qt; library), and the Krusader Krew may not be the right people to address this major issue in any case; so currently this is just a bug we have to learn to live with."
msgstr ""

#. Tag: para
#: faq.docbook:839
#, no-c-format
msgid "When I try to resize &krusader; to make it smaller, I discover that I can't resize it below a certain size. Why?"
msgstr ""

#. Tag: para
#: faq.docbook:844
#, no-c-format
msgid "See the <guibutton>F1, F2</guibutton> (&etc;) buttons? They are not allowing &krusader; to downsize as they have a minimum size. Just disable them <menuchoice> <guimenu>View</guimenu> <guimenuitem>Show FN Keys Bar</guimenuitem> </menuchoice> and you'll be able to resize &krusader; to your liking. Since version 1.51 we have improved this greatly: when downsizing the buttons will look like 'F5 ..py'. When the button faces are too small to read a tooltip will give the complete text. The minimum width is 45 pixels for each button."
msgstr ""

#. Tag: para
#: faq.docbook:865
#, no-c-format
msgid "When I perform some file operations, &krusader;'s panel doesn't refresh / I'm using &krusader; with fam installed, but updates to the panel are not shown. Why?"
msgstr ""

#. Tag: para
#: faq.docbook:871
#, no-c-format
msgid "The bad news is that we're not sure why, but it seems that <command>fam</command> (file alteration monitor) sometimes refuses to work. We are looking into this problem to make sure it is not <emphasis>our</emphasis> problem. We've tried the same source code on two different Gentoo installations: one worked, the other did not. The good news is that if you disable <application>fam</application>, &krusader; will automatically revert to its internal update mechanism (which is less efficient, but works) without needing to recompile. You can disable <application>fam</application> with: <screen><prompt>$</prompt> <userinput><command>su -c 'fam -l'</command></userinput></screen> Look at the manpages for more information about <application>fam</application>."
msgstr ""

#. Tag: para
#: faq.docbook:895
#, no-c-format
msgid "<application>Samba</application> ISO 8859-x codepage / What to do if &krusader; does not read shared directories containing special international characters?"
msgstr ""

#. Tag: para
#: faq.docbook:902
#, no-c-format
msgid ""
      "&krusader; does not handle (yet) <application>Samba</application> ISO 8859-x codepages, if you use a codepage different than 8859-1 you will have to do a manual configuration. Create or modify the file: <filename>~/.smb/smb.conf</filename> <programlisting>[global] 
\n"
      "          workgroup = MyWorkGroup (ex. WORKGROUP) 
\n"
      "          client code page = MyCodePage (ex. 852)
\n"
      "          character set = MyCharSet (ex. ISO8859-2)
\n"
      "          </programlisting> Unfortunately <application>kcontrol</application> (&kde; 3.1.1) fails to configure smb.conf properly, so this must be done manually with a text editor."
msgstr ""

#. Tag: para
#: faq.docbook:923
#, no-c-format
msgid "&krusader; reports \"krarc:... protocol not supported\" error at opening an archive file, what to do?"
msgstr ""

#. Tag: para
#: faq.docbook:928
#, no-c-format
msgid "Install the krarc slave properly:"
msgstr ""

#. Tag: para
#: faq.docbook:929
#, no-c-format
msgid "Copy the <filename>kio_krarc.so</filename>, <filename>kio_krarc.la</filename> files into <filename class=\"directory\"> $KDEDIR/lib/kde3</filename>"
msgstr ""

#. Tag: para
#: faq.docbook:934
#, no-c-format
msgid "Copy the <filename>krarc.protocol</filename> file into <filename class=\"directory\"> $KDEDIR/share/services</filename>"
msgstr ""

#. Tag: para
#: faq.docbook:938
#, no-c-format
msgid "or the directory where the KIO slaves are placed in your &Linux; distribution."
msgstr ""

#. Tag: para
#: faq.docbook:946
#, no-c-format
msgid "I get the error message \"Protocol not supported by Krusader: \"krarc:/path/to/foo-archive\", when I try to open foo-Archive, what to do?"
msgstr ""

#. Tag: para
#: faq.docbook:951
#, no-c-format
msgid "The icons, kio_slaves and documentation must be installed in the correct places in the &kde; directory tree. The <filename>kio_krarc.*</filename> files must be in the same directory with the other KIO slaves. Try this: locate <filename>kio_tar.*</filename> and copy/link the <filename>kio_krarc.*</filename> files to the same location. Don't forget to run <command># ldconfig</command> on this directory when you're done. For more information click <ulink url=\"www.krusader.org/phpBB/viewtopic.php?t=991\"> here</ulink>."
msgstr ""

#. Tag: para
#: faq.docbook:970
#, no-c-format
msgid "What todo if an extenal tool doesn't seem to work?"
msgstr ""

#. Tag: para
#: faq.docbook:973
#, no-c-format
msgid "Krusader uses several programs as <link linkend=\"konfig-dependencies\">external tools</link>, and sometimes they appear not to work. Open a terminal and check if tool foo is installed. <screen><prompt>$</prompt> <userinput><command>foo</command></userinput></screen> Check if tool foo is properly configured in the &konfigdependencie-lnk;. For Archiving tools: autodetect the archives again with the <guibutton>Auto Configure</guibutton> button in the <link linkend=\"konfig-archives\">Konfigurator archive page</link>. Check the &konfigprotocol-lnk; If it doesn't work, backup your <filename>~/.kde/share/config/krusaderrc</filename> configuration file and remove it from this location, Restart Krusader, Krusader will now start the first start configuration wizard, follow these guidelines."
msgstr ""

#. Tag: para
#: faq.docbook:996
#, no-c-format
msgid "Howto executing jar files (and not enter the jar archive)?"
msgstr ""

#. Tag: para
#: faq.docbook:999
#, no-c-format
msgid "Go to the &konfigprotocol-lnk; and remove <guilabel>application/x-jar</guilabel> from the krarc node, &krusader; should no longer enter the archive. Global file associations are handled by &kde; and not by &krusader;. To assosiate the jar extension:"
msgstr ""

#. Tag: para
#: faq.docbook:1005
#, no-c-format
msgid "Open &kde;s control center: <application>kcontrol</application>"
msgstr ""

#. Tag: menuchoice
#: faq.docbook:1010
#, no-c-format
msgid "<guimenu>KDE Components</guimenu> <guimenuitem>File Associations</guimenuitem>"
msgstr ""

#. Tag: para
#: faq.docbook:1017
#, no-c-format
msgid "Enter <filename>jar</filename> as filename pattern"
msgstr ""

#. Tag: para
#: faq.docbook:1021
#, no-c-format
msgid "Add <filename>java</filename> as application"
msgstr ""

#. Tag: para
#: faq.docbook:1033
#, no-c-format
msgid "Why do I have trouble with my &FTP; connection?"
msgstr ""

#. Tag: para
#: faq.docbook:1037
#, no-c-format
msgid "This problem often occurs when you are behind a firewall or proxy. Open <menuchoice> <guimenu>KDE Control Center</guimenu> <guimenuitem>Network</guimenuitem> <guimenuitem>Preferences</guimenuitem> </menuchoice>, <guilabel>\"Enable Passive Mode (PASV)\"</guilabel> has to be turned on or off, depending on it's current setting. Now try your &FTP; session again to see if it works. Also, make sure you have no other &FTP; sessions open (using web browsers, etc.), they can cause complications. More information can be found in &active-passive-ftp-url;."
msgstr ""

#. Tag: para
#: faq.docbook:1058
#, no-c-format
msgid "I get <errorcode>\"FTP protocol not supported by &krusader;\"</errorcode> error when trying to open a remote &FTP; directory, what to do?"
msgstr ""

#. Tag: para
#: faq.docbook:1065
#, no-c-format
msgid "The reason for this error is that '&FTP; via &HTTP; proxy' feature is not yet supported by &krusader;. This error may be caused by a misconfiguration of the proxy settings in &kcontrolcenter;. Modify the proxy settings to not use &HTTP; proxy and &FTP; will work."
msgstr ""

#. Tag: para
#: faq.docbook:1079
#, no-c-format
msgid "How don't add \".part\" suffix when copying files via ftp?"
msgstr ""

#. Tag: para
#: faq.docbook:1082
#, no-c-format
msgid "When uploading files a <filename>.part</filename> suffix is added to the filename, once the upload is complete the filename is renamed automagically to remove the <filename>.part</filename> suffix. This works great but sometimes some ftp-servers don't allow a rename operation. You can solve this by unchecking the checkbox <guilabel>Mark partially uploaded files</guilabel> in &kde;'s control center. The checkbox is located at <menuchoice> <guimenu>Internet and Network</guimenu> <guimenuitem>Connection Preferences</guimenuitem> </menuchoice>."
msgstr ""

#. Tag: para
#: faq.docbook:1099
#, no-c-format
msgid "How can I close a remote connection (&eg; a FTP connection)?"
msgstr ""

#. Tag: para
#: faq.docbook:1103
#, no-c-format
msgid "It's explained in the <link linkend=\"remote-connections\">remote connections chapter</link>."
msgstr ""

#. Tag: para
#: faq.docbook:1112
#, no-c-format
msgid "I am experiencing problems with the media:// protocol, why?"
msgstr ""