faq.docbook.pot

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

msgid "If you've got bugs to report please do not use &kde;'s bugzilla http://bugs.kde.org/, &kde;'s Bug Tracking System. Report &krusader; bugs directly to us."
msgstr ""

#. Tag: para
#: faq.docbook:1506
#, no-c-format
msgid "How can i send good debug or crash reports?"
msgstr ""

#. Tag: para
#: faq.docbook:1509
#, no-c-format
msgid "Usually binary packages that are been used by your distribution do not contain debug information. Since we usually only develop and fix &krusader;-cvs, compile &krusader;-cvs in debugmode and install it, than check if the bug still exist. <screen><prompt>$</prompt> <userinput><command>./configure</command> <option>--enable-debug=full</option></userinput></screen> Install <ulink url=\"http://valgrind.org\">valgrind</ulink>, a suite of tools for debugging and profiling &Linux; programs. Run Valgrind/&krusader; <screen><prompt>$</prompt> <userinput><command>valgrind</command> <option>--tool=memcheck</option> <replaceable>{foo_path}/krusader</replaceable></userinput></screen> The valgrind tool will write to stdout, what really happens. If you could send these informations before the crash, it's almost sure, that we may fix or tell you what to do."
msgstr ""

#. Tag: para
#: faq.docbook:1527
#, no-c-format
msgid "What todo if the KDEcrashhandler sends no usefull backtrace information?"
msgstr ""

#. Tag: para
#: faq.docbook:1530
#, no-c-format
msgid "Usually binary packages that are been used by your distribution do not contain debug information. Since we usually only develop and fix &krusader;-cvs, compile &krusader;-cvs in debugmode and install it, than check if the bug still exist. <screen><prompt>$</prompt> <userinput><command>./configure</command> <option>--enable-debug=full</option></userinput></screen> If the KDEKrashhandler still doesn't provide usefull backtrace information, than sometimes a coredump will give better information. Run Krusader, with disabled crashhandler. <screen><prompt>$</prompt> <userinput><command>krusader</command> <option>--nocrashhandler</option></userinput></screen> On a crash you will get a <filename>.core</filename> file, usually in your home directory. Run <ulink url=\"http://sourceware.org/gdb/\">gdb</ulink>, the GNU Project Debugger <screen><prompt>$</prompt> <userinput><command>gdb</command> <option>-c</option> <replaceable>corefile krusader</replaceable></userinput></screen> Now type <command>bt</command> to get the backtrace and type <command>q</command> to quit gdb. Often the best debug results will be given when using the valgrint tool."
msgstr ""

#. Tag: para
#: faq.docbook:1554
#, no-c-format
msgid "Does &krusader; have a mailing list?"
msgstr ""

#. Tag: para
#: faq.docbook:1558
#, no-c-format
msgid "Yes, currently we have 6 &mailing-lists-url;. No spam, no bother, just &krusader;. Feel free to subscribe and unsubscribe."
msgstr ""

#. Tag: para
#: faq.docbook:1562
#, no-c-format
msgid "Tip. our mailing lists can be browsed online or read with a newsreader, so that you don't even need to subscribe to follow the action on the mailing lists."
msgstr ""

#. Tag: para
#: faq.docbook:1567
#, no-c-format
msgid "&krunews-url; is a very low volume list, used for newsletters and announcements of new versions or critical bugfixes. The news can also be read online at &krulatestnews-url; and in the &newsforum-url; which are basically the same but displayed in another format."
msgstr ""

#. Tag: para
#: faq.docbook:1575
#, no-c-format
msgid "&krudevel-url; is the developer mailing list (read-only). If you want to follow the development of &krusader; on the cutting edge, this is the list to follow."
msgstr ""

#. Tag: para
#: faq.docbook:1581
#, no-c-format
msgid "&kruusers-url; is the &krusader; users mailing list. Here you can ask for help and talk with the &krusader; users and developers."
msgstr ""

#. Tag: para
#: faq.docbook:1587
#, no-c-format
msgid "&krui18n-url; is the translations mailing list."
msgstr ""

#. Tag: para
#: faq.docbook:1591
#, no-c-format
msgid "&krudoc-url; is the documentation mailing list."
msgstr ""

#. Tag: para
#: faq.docbook:1595
#, no-c-format
msgid "&krucommits-url; (read-only): when the &krusader; Krew commits code into CVS, it will be reported in this mailing list. Want to keep track? Waiting for a certain feature/bugfix? Follow &krusader;'s development here."
msgstr ""

#. Tag: para
#: faq.docbook:1609
#, no-c-format
msgid "Does &krusader; provide newsfeeds?"
msgstr ""

#. Tag: para
#: faq.docbook:1613
#, no-c-format
msgid "Yes, we do. Several newsfeeds in various formats are available. &filereleasefeed-url;, &forumfeed-url;, &krunewsfeed-url;, &krudevelfeed-url; and even <ulink url=\"http://dir.gmane.org/gmane.comp.kde.krusader.devel\"> additional feeds</ulink> by gmane.org. &kruusersfeed-url;, &krui18nfeed-url;, &krudocfeed-url;."
msgstr ""

#. Tag: para
#: faq.docbook:1628
#, no-c-format
msgid "Does &krusader; have an IRC channel?"
msgstr ""

#. Tag: para
#: faq.docbook:1632
#, no-c-format
msgid "Yes, we do. Feel free to talk to the &krusader; Krew and fellow-users via &freenode-url; servers. The server is <emphasis>irc.freenode.org</emphasis>, the channel is <emphasis>#krusader</emphasis>. Everyone is welcome."
msgstr ""

#. Tag: para
#: faq.docbook:1644
#, no-c-format
msgid "How does the &krusader; forum work?"
msgstr ""

#. Tag: para
#: faq.docbook:1648
#, no-c-format
msgid "In the spirit of freedom of speech, everything that is &krusader; related can be discussed in our forum. It does not matter if you are a newcomer or an advanced user, everyone is welcome. An open source project's greatest strength is derived from getting user feedback. That is why we love to hear what you have to say. With your feedback we can make &krusader; better and better; otherwise, we are not aware of issues and ideas you may have. But please remember the following, so that we can maintain some order in the chaos."
msgstr ""

#. Tag: para
#: faq.docbook:1659
#, no-c-format
msgid "If the <link linkend=\"index\">Documentation</link>, &faq-lnk;, &kruforum-url; and &krudevel-url; (please use the search function ) can't help you, do not hesitate to post on our forum. The &krusader; Krew or the &krusader; community is always available to help you."
msgstr ""

#. Tag: para
#: faq.docbook:1667
#, no-c-format
msgid "Please use the &kruforumsearch-url; function of the &kruforum-url;, your issue may have been previously discussed (this allows us to minimize the double/triple/... postings). If your issue has already been discussed in the past there is a great chance that you will have an instant solution to your problem. If the issue is currently being discussed, you can join in the discussion. Some questions are asked over and over again, that's why we have created this &faq-lnk;. This allows us to spend more time developing &krusader;."
msgstr ""

#. Tag: para
#: faq.docbook:1678
#, no-c-format
msgid "The &kruforum-url; is split into seven sections:"
msgstr ""

#. Tag: para
#: faq.docbook:1682
#, no-c-format
msgid "&newsforum-url;: all the latest news."
msgstr ""

#. Tag: para
#: faq.docbook:1686
#, no-c-format
msgid "&newsletterforum-url;: all newsletters."
msgstr ""

#. Tag: para
#: faq.docbook:1689
#, no-c-format
msgid "&bugforum-url;: discussions about bugs, please DO NOT use the forum for &faqbugreports-lnk; (except if you are unsure if you have found a bug)."
msgstr ""

#. Tag: para
#: faq.docbook:1695
#, no-c-format
msgid "&featureforum-url;: discussions about new features for future &krusader; versions."
msgstr ""

#. Tag: para
#: faq.docbook:1700
#, no-c-format
msgid "&todoforum-url; here you will find the list of the planned features. Registered users will be able to VOTE and COMMENT on the TODO items. Here you get the chance to push your favourite features (+3) and still prefer certain features over others (+1), if you don't care about a feature just simply don't vote on that feature. Unregistered users may only browse the &todoforum-url;. The &todoranking-url; contains the results based on the votes. <link linkend=\"faqg_patch\">Adding ToDo items</link> or removing ToDo items which have been implemented will be done by the &krusader; Krew."
msgstr ""

#. Tag: para
#: faq.docbook:1715
#, no-c-format
msgid "&useractionsforum-url;: discussions about &useractions-lnk;. Posting your own User Actions is greatly appreciated. We plan to include the best ones in the next &krusader; releases."
msgstr ""

#. Tag: para
#: faq.docbook:1722
#, no-c-format
msgid "&krugenforum-url;: everything that is &krusader; related and doesn't belong in the other forums."
msgstr ""

#. Tag: para
#: faq.docbook:1728
#, no-c-format
msgid "We provide RSS feeds for our forums. You don't have to check for new posts all the time, instead the news will come to you! To make use of them, simply point your RSS aggregator to &rss-url;."
msgstr ""

#. Tag: para
#: faq.docbook:1738
#, no-c-format
msgid "How can I translate &krusader; into my native language?"
msgstr ""

#. Tag: para
#: faq.docbook:1742
#, no-c-format
msgid "Please read the &i18n-page-url;. It's not difficult to translate! Most anyone can do it, it just takes some time."
msgstr ""

#. Tag: para
#: faq.docbook:1751
#, no-c-format
msgid "How can I support &krusader;?"
msgstr ""

#. Tag: para
#: faq.docbook:1754
#, no-c-format
msgid "You can <link linkend=\"help_krusader\"> support</link> &krusader; in many different ways. Please send us <link linkend=\"faqg_wish\">feedback</link>, &faqbugreports-lnk;, patches, <link linkend=\"help_krusader\">donations</link>, translations, ..."
msgstr ""

#. Tag: para
#: faq.docbook:1768
#, no-c-format
msgid "Is there a &MacOS; X port?"
msgstr ""

#. Tag: para
#: faq.docbook:1771
#, no-c-format
msgid "Yes, there is &MacOS; X port, but you will not have the all the power you would have on &Linux;. Please read the <link linkend=\"mac-port\">&MacOS; X port section</link> for more information. A recommended native file manager for &MacOS; is &disk-order-url; (shareware)."
msgstr ""

#. Tag: para
#: faq.docbook:1784
#, no-c-format
msgid "Is there a &Windows; port?"
msgstr ""

#. Tag: para
#: faq.docbook:1787
#, no-c-format
msgid "No, but this might change in the future. Please <link linkend=\"help_krusader\">help us</link> with this project, contributions are greatly appreciated. A recommended native file manager for &Windows; is &tcmd-url; (shareware)."
msgstr ""

#. Tag: para
#: faq.docbook:1798
#, no-c-format
msgid "Why is &konqueror; in \"midnight commander style\" not an <link linkend=\"gloss-ofm\">OFM</link>?"
msgstr ""

#. Tag: para
#: faq.docbook:1803
#, no-c-format
msgid "The two panels and a commandline are available, all the other stuff like <link linkend=\"features\">OFM features</link> and the <link linkend=\"gloss-ofm\">OFM</link> interaction with the user is missing from this profile."
msgstr ""

#. Tag: para
#: faq.docbook:1814
#, no-c-format
msgid "Why should I use an <link linkend=\"gloss-ofm\">OFM</link>?"
msgstr ""

#. Tag: para
#: faq.docbook:1818
#, no-c-format
msgid "An &ofm-url; is much faster than a one panel filemanager and faster than the command line. If you would like to know <ulink url=\"http://www.softpedia.com/reviews/linux/Krusader-Review-18193.shtml\"> how &krusader; feels</ulink>, there is only one way to discover: install it on your computer and use it for a while. If you prefer to waste time and lose productivity, continue to use one panel filemanagers which are based on &Windows; Explorer. Matej Urban&ccaron;i&ccaron; has written a <ulink url=\"http://murban.blogspot.com/2006/01/krusader-and-konqueror-twin-versus-one.html\"> blog</ulink>on why <link linkend=\"gloss-ofm\">OFM</link> is better than a one panel filemanager."
msgstr ""