useractions.docbook.pot

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

# Translation of useractions.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
#: useractions.docbook:22
#, no-c-format
msgid "<title>UserActions</title>"
msgstr ""

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

#. Tag: para
#: useractions.docbook:27
#, no-c-format
msgid "With ActionMan you can set up, configure and manage UserActions. Some general settings are configured with <link linkend=\"konfig-useractions\">Konfigurator</link>. With UserActions you can perform actions on files in the panel or to access &krusader; internal functions with parameters directly using placeholders. The actions integrate seamlessly into &kde;'s action system, which means that the standard Edit Toolbar and Edit Shortcut dialogs will show UserActions, too. The UserActions are stored in <filename> ~/.kde/share/apps/krusader/useraction.xml</filename> (the file structure is documentated in doxygen headers of UserActionXML). Several <link linkend=\"useraction-xml\">examples</link> are included in the documentation. UserActions can be edited / added / imported / exported by using ActionMan. The default UserActions are stored in <filename> ~/.kde/share/apps/krusader/useraction-examples.xml</filename>. UserActions can appear nearly everywhere where \"normal\" KActions can be placed. The actions integrate seamlessly into &kde; action system, which means that the standard Edit Toolbar and Edit Shortcut dialogs will show UserActions, too. They can even be placed in the menu bar, but for that the <filename>krusaderui.rc</filename> file must be edited. A few examples: <itemizedlist> <listitem> <para> <link linkend=\"useractions-menu\">Useractions Menu</link> </para> </listitem> <listitem> <para>&usermenu-lnk;</para> </listitem> <listitem> <para>&actions-toolbar-lnk;</para> </listitem> <listitem> <para>right click menus</para> </listitem> <listitem> <para>&etc;</para> </listitem> </itemizedlist>&krusader;'s UserActions tool is very powerful and customizable if you are familiar with writing UserActions in general."
msgstr ""

#. Tag: para
#: useractions.docbook:75
#, no-c-format
msgid "Several UserActions are provided by default. Please <link linkend=\"help_krusader\">upload your favorite UserActions</link> so that they become available for the &krusader; community. Thanks! We provide also an &useractionsforum-url;."
msgstr ""

#. Tag: title
#: useractions.docbook:82
#, no-c-format
msgid "<title>ActionMan</title>"
msgstr ""

#. Tag: phrase
#: useractions.docbook:88
#, no-c-format
msgid "<phrase>ActionMan</phrase>"
msgstr ""

#. Tag: para
#: useractions.docbook:92
#, no-c-format
msgid "Basically, UserActions are a method to call external programs with variable parameters. For example, you could have a UserAction with the following <command>xmms <option>--enqueue %aList(\"Selected\")%</option></command> to enqueue all selected items of the active panel to the current instance of xmms. Additionally, there is limited access to &krusader; internal functions requiring parameters. For example, <command>%aPanelSize(\"80\")%</command> will set the width of the active panel to 80% of the &krusader; mainwindow. Since the parameter of placeholders can contain other placeholders, few scripts are possible. However, scripting can be done with the &javascript-console-lnk;."
msgstr ""

#. Tag: emphasis
#: useractions.docbook:107
#, no-c-format
msgid "Managing UserActions"
msgstr ""

#. Tag: para
#: useractions.docbook:109
#, no-c-format
msgid "Open Konfigurator and choose \"UserActions -&gt; ActionMan\", in which you can add, edit, remove, import and export UserActions. <itemizedlist> <listitem> <para> <guimenuitem>Add Action</guimenuitem>: If you add an new action, you get an empty input mask where you can enter all the properties you desire. The action will be added as soon as you press <guimenuitem>Ok</guimenuitem>. Afterwards, the name is shown in the list on the left.</para> </listitem> <listitem> <para>To edit a UserAction: Select the UserAction on the left. Then choose it if you want to edit its properties. The changes will only take effect when you press <guimenuitem>OK</guimenuitem>.</para> </listitem> <listitem> <para> <guimenuitem>To remove a UserAction</guimenuitem>: Select the UserAction on the left and click the remove button.</para> </listitem> <listitem> <para> <guimenuitem>To import a UserAction</guimenuitem>: If you import some actions, they will be automatically added to your list. If there are name conflicts (the names have to be unique because these are the ID for &kde;'s action system), you are asked to resolve them. For this, the list on the left will only show the actions where conflicts exist. You can now give them new names or remove them.</para> </listitem> <listitem> <para> <guimenuitem>Export Action</guimenuitem>: If you export a UserAction you have to give a filename in which to store it. If it does not exist, it will be created. If the file already contains UserActions, the action you are exporting will be added to that file.</para> </listitem> </itemizedlist>All actions you have defined are now shown in the user menu and in &kde; dialogs for changing shortcuts and managing the toolbar. In addition, all actions available for the current item will also show up in the right click menu."
msgstr ""

#. Tag: guimenuitem
#: useractions.docbook:158
#, no-c-format
msgid "Basic Properties"
msgstr ""

#. Tag: para
#: useractions.docbook:161
#, no-c-format
msgid "<guimenuitem>\"Distinct Name\", \"Title\" and \"Command line\"</guimenuitem>are always required, all the other properties are optional."
msgstr ""

#. Tag: para
#: useractions.docbook:167
#, no-c-format
msgid "<guimenuitem>\"Distinct Name\"</guimenuitem>: A unique name of the UserAction, used to identify it for &kde;'s action system."
msgstr ""

#. Tag: para
#: useractions.docbook:173
#, no-c-format
msgid "<guimenuitem>\"Icon button\"</guimenuitem>: The icon for your UserAction."
msgstr ""

#. Tag: para
#: useractions.docbook:178
#, no-c-format
msgid "<guimenuitem>\"Category\"</guimenuitem>: Adds a category for a better overview. NOTE: This property is not used yet. It is planned to be used, but has not implemented yet."
msgstr ""

#. Tag: para
#: useractions.docbook:184
#, no-c-format
msgid "<guimenuitem>\"Title\"</guimenuitem>: The title displayed in the menus or dialogs."
msgstr ""

#. Tag: para
#: useractions.docbook:189
#, no-c-format
msgid "<guimenuitem>\"Tooltip\"</guimenuitem>: A tooltip for your UserAction, &eg; displayed in the toolbar on mouseover."
msgstr ""

#. Tag: para
#: useractions.docbook:195
#, no-c-format
msgid "<guimenuitem>\"Description\"</guimenuitem>: A description of what the UserAction does. This is also displayed as <guimenuitem>\"What's This\"</guimenuitem> if you <keycombo action=\"simul\">&Shift; <keycap>F1</keycap></keycombo> click on your UserAction."
msgstr ""

#. Tag: para
#: useractions.docbook:204
#, no-c-format
msgid "<guimenuitem>\"Use Tooltip checkbox\"</guimenuitem>: Uses the tooltip as description."