[nautilus-actions] Add i18n comments to NACT user's manual
- From: Pierre Wieser <pwieser src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [nautilus-actions] Add i18n comments to NACT user's manual
- Date: Wed, 10 Oct 2012 19:32:03 +0000 (UTC)
commit acba359ada7fce37efa0ad7eec8ce0754c06f623
Author: Pierre Wieser <pwieser trychlos org>
Date: Wed Oct 10 21:30:58 2012 +0200
Add i18n comments to NACT user's manual
Fix #667429 Are this strings translatable ?
Reported by Daniel Mustieles.
docs/nact/C/nact-conditions.xml | 299 +++++++++++++++++++++++++--------------
docs/nact/C/nact-edit.xml | 3 +-
docs/nact/C/nact-execution.xml | 101 ++++++++-----
docs/nact/C/nact-menus.xml | 37 +++--
docs/nact/C/nact-misc.xml | 15 ++-
docs/nact/C/nact-prefs.xml | 2 +
docs/nact/C/nact-profiles.xml | 19 ++-
docs/nact/C/nact-properties.xml | 2 +-
docs/nact/C/nact-save.xml | 7 +-
docs/nact/C/nact-sorting.xml | 14 +-
docs/nact/C/nact-starting.xml | 154 ++++++++++++--------
docs/nact/C/nact-where.xml | 27 +++--
12 files changed, 430 insertions(+), 250 deletions(-)
---
diff --git a/docs/nact/C/nact-conditions.xml b/docs/nact/C/nact-conditions.xml
index e83efef..e0a3ee4 100644
--- a/docs/nact/C/nact-conditions.xml
+++ b/docs/nact/C/nact-conditions.xml
@@ -25,6 +25,7 @@
decide that none of the selected item(s) can have some other sort of basename.
</para>
<para>
+ <!-- i18n: "Basenames" is a UI label -->
Click on the <guilabel>Basenames</guilabel> tab to show the page
which will permit you to configure your basename-based conditions.
</para>
@@ -47,11 +48,11 @@
<para>
In fact, basename-based conditions are built as a list of
&must_match; and &must_not_match;
- patterns. In order for your action to be a candidate regarding these basename-based
- conditions, each element of the selection must be valid for all the listed
- conditions: the basename of each element must match at least one of the defined
- &must_match; patterns, and must not match any of
- the defined &must_not_match; patterns.
+ patterns. In order for your action to be a candidate regarding these
+ basename-based conditions, each element of the selection must be valid
+ for all the listed conditions: the basename of each element must match
+ at least one of the defined &must_match; patterns, and must not match
+ any of the defined &must_not_match; patterns.
</para>
<para>
If at least one element of the selection does not match all the defined
@@ -74,6 +75,7 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Insert" is a key name -->
Press <keycap>Insert</keycap> or click on
<guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
button to insert a new condition filter
@@ -81,7 +83,8 @@
</listitem>
<listitem>
<para>
- Edit the newly inserted condition filter to the basename you want match.
+ Edit the newly inserted condition filter to the basename you
+ want match.
</para>
<tip>
<para>
@@ -98,21 +101,26 @@
or a &must_not_match; condition.
</para>
<para>
+ <!-- i18n: "Must match one of" is a UI label -->
Click on the <guilabel>Must match one of</guilabel> or
- <guilabel>Must not match any of</guilabel> radio button in the same
- row to set the corresponding condition.
+ <!-- i18n: "Must not match any of" is a UI label -->
+ <guilabel>Must not match any of</guilabel> radio button in the
+ same row to set the corresponding condition.
</para>
</listitem>
</orderedlist>
<para>
Depending of your target operating system, make sure that the
+ <!-- i18n: "Match case" is a UI label -->
<guilabel>Match case</guilabel> checkbox is activated (or not).
</para>
<itemizedlist>
<listitem>
<para>
When activated, all filters are considered as case sensitive,
+ <!-- i18n: "/my/file" is an example of *nix filename, and may be translated -->
which means that <filename>/my/file</filename> filename is
+ <!-- i18n: "/My/File" is an example of *nix filename, and may be translated -->
considered distinct from <filename>/My/File</filename> one.
</para>
<para>
@@ -122,7 +130,9 @@
<listitem>
<para>
When deactivated, filters are considered as case insensitive,
+ <!-- i18n: "/my/file" is an example of *nix filename, and may be translated -->
which means that <filename>/my/file</filename> and
+ <!-- i18n: "/My/File" is an example of *nix filename, and may be translated -->
<filename>/My/File</filename> filenames are considered the same
name.
</para>
@@ -134,12 +144,14 @@
</itemizedlist>
<para>
Removing a defined basename-based condition is as simple as selecting
+ <!-- i18n: "Del" is a key name -->
it, and pressing <keycap>Del</keycap> (or clicking on
<guibutton><inlinegraphic fileref="figures/remove.png"/></guibutton>
button).
</para>
<para>
By default, the basename-based condition is just one
+ <!-- i18n: "must match one of" matches a UI label, may be translated -->
«sp;<literal>must match one of *</literal>&spraquo; condition.
As all basenames always match the &asterisk;
condition, this just means that basename-based conditions are not
@@ -151,11 +163,13 @@
<title>Mimetype-based conditions</title>
<para>
You may decide that your action will appear depending on the mimetypes
- of the items currently selected in the file-manager: you may define that each
- item of the selection must meet some sort of mimetype; and you may simultaneously
- decide that none of the selected item(s) can have some other sort of mimetype.
+ of the items currently selected in the file-manager: you may define
+ that each item of the selection must meet some sort of mimetype; and
+ you may simultaneously decide that none of the selected item(s) can
+ have some other sort of mimetype.
</para>
<para>
+ <!-- i18n: "Mimetypes" is a UI label -->
Click on the <guilabel>Mimetypes</guilabel> tab to show the page
which will permit you to configure your mimetype-based conditions.
</para>
@@ -178,22 +192,24 @@
<para>
In fact, mimetype-based conditions are built as a list of
&must_match; and &must_not_match; patterns.
- In order for your action to be a candidate regarding these mimetype-based
- conditions, each element of the selection must be valid for all the listed
- conditions: the mimetype of each element must match at least one of the defined
- &must_match; patterns, and must not match any of
- the defined &must_not_match; patterns.
+ In order for your action to be a candidate regarding these
+ mimetype-based conditions, each element of the selection must be
+ valid for all the listed conditions: the mimetype of each element
+ must match at least one of the defined &must_match; patterns, and
+ must not match any of the defined &must_not_match; patterns.
</para>
<para>
- If at least one element of the selection does not match all the defined
- conditions, then your action will not be displayed.
+ If at least one element of the selection does not match all the
+ defined conditions, then your action will not be displayed.
</para>
<para>
- When targeting the selection context menu, your mimetype-based conditions
- will be checked against the currently selected items. When targeting the
- location context menu or the toolbar, your mimetype-based conditions will
- be checked against the mimetype of the current location, which happens to
- be the well known «sp;inode/directory&spraquo; mimetype.
+ When targeting the selection context menu, your mimetype-based
+ conditions will be checked against the currently selected items.
+ When targeting the location context menu or the toolbar, your
+ mimetype-based conditions will be checked against the mimetype of
+ the current location, which happens to be the well known
+ <!-- i18n: "inode/directory" is a mimetype, not translatable -->
+ «sp;inode/directory&spraquo; mimetype.
</para>
<para>
Defining a new mimetype-based condition involves two steps.
@@ -206,6 +222,7 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Insert" is a key name -->
Press <keycap>Insert</keycap> or click on
<guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
button to insert a new condition filter
@@ -213,15 +230,19 @@
</listitem>
<listitem>
<para>
- Edit the newly inserted condition filter to the mimetype you want match.
+ Edit the newly inserted condition filter to the mimetype
+ you want match.
</para>
<para>
- A mimetype must be defined as a <literal>group/subgroup</literal>
+ A mimetype must be defined as a
+ <!-- i18n: "group/subgroup" stands for a mimetype template, may be translated -->
+ <literal>group/subgroup</literal>
expression.
</para>
<tip>
<para>
- The &asterisk; wildcard is supported only in some situations:
+ The &asterisk; wildcard is supported only in some
+ situations:
</para>
<itemizedlist>
<listitem>
@@ -233,12 +254,15 @@
</listitem>
<listitem>
<para>
+ <!-- i18n: "group" stands for the first part of a mimetype, may be translated -->
A <literal>group/*</literal> string
+ <!-- i18n: "group" stands for the first part of a mimetype, may be translated -->
matches all subgroups of <literal>group</literal> mimetype.
</para>
</listitem>
<listitem>
<para>
+ <!-- i18n: "subgroup" stands for the second part of a mimetype, may be translated -->
The <literal>*/subgroup</literal> string
is not accepted as a valid wildcard.
</para>
@@ -250,23 +274,28 @@
</listitem>
<listitem>
<para>
- Indicates whether this a &must_match; or a &must_not_match; condition.
+ Indicates whether this a &must_match; or a &must_not_match;
+ condition.
</para>
<para>
+ <!-- "Must match one of" is a UI label -->
Click on the <guilabel>Must match one of</guilabel> or
- <guilabel>Must not match any of</guilabel> radio button in the same
- row to set the corresponding condition.
+ <!-- "Must not match any of" is a UI label -->
+ <guilabel>Must not match any of</guilabel> radio button in the
+ same row to set the corresponding condition.
</para>
</listitem>
</orderedlist>
<para>
- Removing a defined mimetype-based condition is as simple as selecting
- it, and pressing <keycap>Del</keycap> (or clicking on
+ Removing a defined mimetype-based condition is as simple as
+ <!-- i18n: "Del" is a key name -->
+ selecting it, and pressing <keycap>Del</keycap> (or clicking on
<guibutton><inlinegraphic fileref="figures/remove.png"/></guibutton>
button).
</para>
<para>
By default, the mimetype-based condition is just one
+ <!-- i18n: "must match one of */*" matches a UI label, and may be translated -->
«sp;<literal>must match one of */*</literal>&spraquo; condition.
As all mimetypes always match the «sp;<literal>*/*</literal>&spraquo;,
this just means that mimetypes are not considered as relevant
@@ -277,6 +306,7 @@
<variablelist>
<varlistentry>
<term>
+ <!-- i18n: "all/all" is a mimetype, not translatable -->
<literal>all/all</literal>
</term>
<listitem>
@@ -287,6 +317,7 @@
</varlistentry>
<varlistentry>
<term>
+ <!-- i18n: "all/allfiles" is a mimetype, not translatable -->
<literal>all/allfiles</literal>
</term>
<listitem>
@@ -297,6 +328,7 @@
</varlistentry>
<varlistentry>
<term>
+ <!-- i18n: "inode/directory" is a mimetype, not translatable -->
<literal>inode/directory</literal>
</term>
<listitem>
@@ -312,12 +344,12 @@
<sect3 id="usage-conditions-folders">
<title>Folder-based conditions</title>
<para>
- You may decide that your action will appear depending on the directory
- the items currently selected in the file-manager are located in:
- you may define that each item of the selection must be located in one
- hierarchy or in another; and you may simultaneously
- decide that none of the selected item(s) can be located in some other
- hierarchy.
+ You may decide that your action will appear depending on the
+ directory the items currently selected in the file-manager are
+ located in: you may define that each item of the selection must
+ be located in one hierarchy or in another; and you may simultaneously
+ decide that none of the selected item(s) can be located in some
+ other hierarchy.
</para>
<para>
A folder-based condition must be understood as the specification
@@ -325,6 +357,7 @@
should not) stay: this is a pattern on the dirname of the element.
</para>
<para>
+ <!-- i18n: "Folders" is a UI label -->
Click on the <guilabel>Folders</guilabel> tab to show the page
which will permit you to configure your folder-based conditions.
</para>
@@ -347,11 +380,11 @@
<para>
In fact, folder-based conditions are built as a list of
&must_match; and &must_not_match; patterns.
- In order for your action to be a candidate regarding these folder-based
- conditions, each element of the selection must be valid for all the
- listed conditions: each element must be located in one of the defined
- &must_match; folders, and must not match any of the defined
- &must_not_match; folders.
+ In order for your action to be a candidate regarding these
+ folder-based conditions, each element of the selection must be
+ valid for all the listed conditions: each element must be located
+ in one of the defined &must_match; folders, and must not match
+ any of the defined &must_not_match; folders.
</para>
<para>
If at least one element of the selection does not match all the
@@ -376,6 +409,7 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Insert" is a key name -->
Press <keycap>Insert</keycap> or click on
<guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
button to insert a new condition filter
@@ -383,7 +417,8 @@
</listitem>
<listitem>
<para>
- Edit the newly inserted condition filter to the folder you want match.
+ Edit the newly inserted condition filter to the folder you
+ want match.
</para>
<tip>
<para>
@@ -407,20 +442,24 @@
condition.
</para>
<para>
+ <!-- i18n: "Must match one of" is a UI label -->
Click on the <guilabel>Must match one of</guilabel> or
- <guilabel>Must not match any of</guilabel> radio button in the same
- row to set the corresponding condition.
+ <!-- i18n: "Must not match any of" is a UI label -->
+ <guilabel>Must not match any of</guilabel> radio button in
+ the same row to set the corresponding condition.
</para>
</listitem>
</orderedlist>
<para>
- Removing a defined folder-based condition is as simple as selecting
- it, and pressing <keycap>Del</keycap> (or clicking on
+ Removing a defined folder-based condition is as simple as
+ <!-- i18n: "Del" is a key name -->
+ selecting it, and pressing <keycap>Del</keycap> (or clicking on
<guibutton><inlinegraphic fileref="figures/remove.png"/></guibutton>
button).
</para>
<para>
By default, the folder-based condition is just one
+ <!-- i18n: "must match one of /" matches a UI label -->
«sp;<literal>must match one of /</literal>&spraquo; condition.
As <literal>/</literal> is always the top of an Unix-like file system,
then all selected items always match this condition.
@@ -436,13 +475,14 @@
<sect3 id="usage-conditions-schemes">
<title>Scheme-base-conditions</title>
<para>
- You may decide that your action will appear depending on the schemes
- of the URIs of the items currently selected in the file-manager:
- you may define that each item of the selection must have some scheme;
- and you may simultaneously
- decide that none of the selected item(s) may have some other scheme.
+ You may decide that your action will appear depending on the
+ schemes of the URIs of the items currently selected in the
+ file-manager: you may define that each item of the selection must
+ have some scheme; and you may simultaneously decide that none of
+ the selected item(s) may have some other scheme.
</para>
<para>
+ <!-- i18n: "Schemes" is a UI label -->
Click on the <guilabel>Schemes</guilabel> tab to show the page
which will permit you to configure your scheme-based conditions.
</para>
@@ -465,21 +505,22 @@
<para>
In fact, scheme-based conditions are built as a list of
&must_match; and &must_not_match; patterns.
- In order for your action to be a candidate regarding these scheme-based
- conditions, each element of the selection must be valid for all the
- listed conditions: the scheme of each element must match at least one
- of the defined &must_match; patterns, and must not match any of
- the defined &must_not_match; patterns.
+ In order for your action to be a candidate regarding these
+ scheme-based conditions, each element of the selection must be
+ valid for all the listed conditions: the scheme of each element
+ must match at least one of the defined &must_match; patterns, and
+ must not match any of the defined &must_not_match; patterns.
</para>
<para>
- If at least one element of the selection does not match all the defined
- conditions, then your action will not be displayed.
+ If at least one element of the selection does not match all the
+ defined conditions, then your action will not be displayed.
</para>
<para>
- When targeting the selection context menu, your scheme-based conditions
- will be checked against the currently selected items. When targeting the
- location context menu or the toolbar, your scheme-based conditions will
- be checked against the scheme of the current location.
+ When targeting the selection context menu, your scheme-based
+ conditions will be checked against the currently selected items.
+ When targeting the location context menu or the toolbar, your
+ scheme-based conditions will be checked against the scheme of
+ the current location.
</para>
<para>
Defining a new scheme-based condition involves two steps.
@@ -492,6 +533,7 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Insert" is a key name -->
Press <keycap>Insert</keycap> or click on
<guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
button to insert a new condition filter
@@ -499,7 +541,8 @@
</listitem>
<listitem>
<para>
- Edit the newly inserted condition filter to the scheme you want match.
+ Edit the newly inserted condition filter to the scheme you
+ want match.
</para>
<tip>
<para>
@@ -511,10 +554,13 @@
<listitem>
<para>
Or click on
+ <!-- i18n: "Common" is a UI (button) label -->
<guibutton>Common</guibutton> to select a scheme among those
predefined in
<menuchoice>
+ <!-- i18n: "Edit" is a menu item -->
<guimenu>Edit</guimenu>
+ <!-- i18n: "Preferences" is a menu item -->
<guimenuitem>Preferences</guimenuitem>
</menuchoice>.
</para>
@@ -535,22 +581,26 @@
</screenshot>
</figure>
<para>
- A new scheme may only be selected here if it is not already
- defined as a scheme filter.
+ A new scheme may only be selected here if it is not
+ already defined as a scheme filter.
</para>
<para>
- To select a new scheme, click <guibutton>OK</guibutton>, or
- double-click on the desired row.
+ <!-- i18n: "OK" is a UI (button) label -->
+ To select a new scheme, click <guibutton>OK</guibutton>,
+ or double-click on the desired row.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
- Indicates whether this a &must_match; or a &must_not_match; condition.
+ Indicates whether this a &must_match; or a &must_not_match;
+ condition.
</para>
<para>
+ <!-- i18n: "Must match one of" is a UI label -->
Click on the <guilabel>Must match one of</guilabel> or
+ <!-- i18n: "Must not match any of" is a UI label -->
<guilabel>Must not match any of</guilabel> radio button
in the same row to set the corresponding condition.
</para>
@@ -558,12 +608,14 @@
</orderedlist>
<para>
Removing a defined scheme-based condition is as simple as selecting
+ <!-- i18n: "Del" is a key name -->
it, and pressing <keycap>Del</keycap> (or clicking on
<guibutton><inlinegraphic fileref="figures/remove.png"/></guibutton>
button).
</para>
<para>
By default, the scheme-based condition is just one
+ <!-- i18n: "must match one of *" matches a UI label -->
«sp;<literal>must match one of *</literal>&spraquo; condition,
which means that schemes are not relevant for this action.
</para>
@@ -572,9 +624,11 @@
<sect3 id="usage-conditions-capabilities">
<title>Capability-based conditions</title>
<para>
- Capabilities are some properties that a file may exhibit to the user.
+ Capabilities are some properties that a file may exhibit to the
+ user.
</para>
<para>
+ <!-- i18n: "Local" is a capability keyword, not translatable -->
But except for the <literal>Local</literal> capability, all others
depend on the user who executes the command.
</para>
@@ -584,6 +638,7 @@
the current user.
</para>
<para>
+ <!-- i18n: "Capabilities" is a UI label -->
Click on the <guilabel>Capabilities</guilabel> tab to show the page
which will permit you to configure your capability-based conditions.
</para>
@@ -606,21 +661,23 @@
<para>
In fact, capability-based conditions are built as a list of
«sp;must match all of&spraquo; and &must_not_match; patterns.
- In order for your action to be a candidate regarding these capability-based
- conditions, each element of the selection must be valid for all the
- listed conditions: the capability of each element must match each
- of the defined «sp;must match all of&spraquo; capabilities,
- and must not match any of the defined &must_not_match; ones.
+ In order for your action to be a candidate regarding these
+ capability-based conditions, each element of the selection must be
+ valid for all the listed conditions: the capability of each element
+ must match each of the defined «sp;must match all of&spraquo;
+ capabilities, and must not match any of the defined &must_not_match;
+ ones.
</para>
<para>
- If at least one element of the selection does not match all the defined
- conditions, then your action will not be displayed.
+ If at least one element of the selection does not match all the
+ defined conditions, then your action will not be displayed.
</para>
<para>
- When targeting the selection context menu, your capability-based conditions
- will be checked against the currently selected items. When targeting the
- location context menu or the toolbar, your capability-based conditions will
- be checked against those of of the current location.
+ When targeting the selection context menu, your capability-based
+ conditions will be checked against the currently selected items.
+ When targeting the location context menu or the toolbar, your
+ capability-based conditions will be checked against those of the
+ current location.
</para>
<para>
Defining a new capability-based condition involves two steps.
@@ -633,18 +690,22 @@
<itemizedlist>
<listitem>
<para>
- Press <keycap>Insert</keycap> to insert a new condition filter
+ <!-- i18n: "Insert" is a key name -->
+ Press <keycap>Insert</keycap> to insert a new condition
+ filter.
</para>
</listitem>
<listitem>
<para>
- Edit the newly inserted condition filter to the capability you want match.
+ Edit the newly inserted condition filter to the capability
+ you want match.
</para>
</listitem>
<listitem>
<para>
Or click on
<guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
+ <!-- i18n: "Adding a new capability" is a UI (dialog title) label -->
to open the <guilabel>Adding a new capability</guilabel> dialog
box.
</para>
@@ -665,12 +726,13 @@
</screenshot>
</figure>
<para>
- A new capability may only be selected here if it is not already
- defined as a capability filter.
+ A new capability may only be selected here if it is not
+ already defined as a capability filter.
</para>
<para>
- To select a new capability, click <guibutton>OK</guibutton>, or
- double-click on the desired row.
+ <!-- i18n: "OK" is a UI (button) label -->
+ To select a new capability, click <guibutton>OK</guibutton>,
+ or double-click on the desired row.
</para>
</listitem>
</itemizedlist>
@@ -681,21 +743,24 @@
or a &must_not_match; condition.
</para>
<para>
+ <!-- i18n: "Must match all of" is a UI label -->
Click on the <guilabel>Must match all of</guilabel> or
- <guilabel>Must not match any of</guilabel> radio button in the same
- row to set the corresponding condition.
+ <!-- i18n: "Must not match any of" is a UI label -->
+ <guilabel>Must not match any of</guilabel> radio button in the
+ same row to set the corresponding condition.
</para>
</listitem>
</orderedlist>
<para>
- Removing a defined capability-based condition is as simple as selecting
- it, and pressing <keycap>Del</keycap> (or clicking on
+ Removing a defined capability-based condition is as simple as
+ <!-- i18n: "Del" is a key name -->
+ selecting it, and pressing <keycap>Del</keycap> (or clicking on
<guibutton><inlinegraphic fileref="figures/remove.png"/></guibutton>
button).
</para>
<para>
- By default, the capability-based condition list is empty. This means
- that capabilities are not relevant for this action.
+ By default, the capability-based condition list is empty. This
+ means that capabilities are not relevant for this action.
</para>
</sect3>
@@ -711,12 +776,15 @@
<para>
If your action consists in displaying the differences between
two files, you may define here
+ <!-- i18n: "Count = (equal to) 2" is a UI label -->
«sp;<literal>Count = (equal to) 2</literal>&spraquo;.
</para>
</example>
<para>
- Click on the <guilabel>Environment</guilabel> tab to show the page
- which will permit you to configure your environment-based conditions.
+ <!-- i18n: "Environment" is a UI label -->
+ Click on the <guilabel>Environment</guilabel> tab to show the
+ page which will permit you to configure your environment-based
+ conditions.
</para>
<figure id="nact-FIG-tab-environment">
<title>Environment-based conditions</title>
@@ -740,6 +808,7 @@
</figure>
<para>
The selection count condition is defined in the
+ <!-- i18n: "Appears if selection contains" is a UI label -->
<guilabel>Appears if selection contains</guilabel> frame.
</para>
<figure id="nact-FIG-frame-count">
@@ -773,12 +842,16 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Count" is a UI label -->
Select in the <guilabel>Count</guilabel> drop-down list
the operator you want apply to the selection count:
</para>
<simplelist type="vert">
+ <!-- i18n: "strictly less than" is a UI label -->
<member><literal><</literal> <termdef>(strictly less than)</termdef></member>
+ <!-- i18n: "equal to" is a UI label -->
<member><literal>=</literal> <termdef>(equal to)</termdef></member>
+ <!-- i18n: "strictly greater than" is a UI label -->
<member><literal>></literal> <termdef>(strictly greater than)</termdef></member>
</simplelist>
</listitem>
@@ -790,6 +863,7 @@
</itemizedlist>
<para>
The selection count defaults to
+ <!-- i18n: "Count > (strictly greater than) 0" is a UI label -->
«sp;<literal>Count > (strictly greater than) 0</literal>&spraquo;,
which means that the action will be a candidate to be displayed
as soon as at least one item is selected in the file manager.
@@ -822,11 +896,13 @@
Only one choice between these three items is possible.
</para>
<para>
+ <!-- i18n: "Environment" is a UI label -->
Click on the <guilabel>Environment</guilabel> tab to show the page
which will permit you to configure your environment-based conditions.
</para>
<para>
The desktop selection is defined in the
+ <!-- i18n: "Desktop environment" is a UI label -->
<guilabel>Desktop environment</guilabel> frame.
</para>
<figure id="nact-FIG-frame-desktop">
@@ -874,6 +950,7 @@
</orderedlist>
<para>
The targeted desktop environment condition defaults to
+ <!-- i18n: "Always appear" is a UI label -->
«sp;<literal>Always appear</literal>&spraquo;,
which means that the action will be a candidate to be displayed
regardless of the current desktop environment.
@@ -890,11 +967,13 @@
present on the file system, and executable.
</para>
<para>
+ <!-- i18n: "Environment" is a UI label -->
Click on the <guilabel>Environment</guilabel> tab to show the page
which will permit you to configure your environment-based conditions.
</para>
<para>
The executable found condition is defined in the
+ <!-- i18n: "Execution environment" is a UI label -->
<guilabel>Execution environment</guilabel> frame.
</para>
<figure id="nact-FIG-frame-execution-environment">
@@ -918,6 +997,7 @@
<para>
To define the relevant file, enter its full filename in the
<guilabel>Appears if the file is executable</guilabel> entry
+ <!-- i18n: "Browse" is a UI (button) label -->
box, or click on <guibutton>Browse</guibutton> to select a file
on the file system.
</para>
@@ -928,8 +1008,8 @@
<tip>
<para>
You may embed some parameters in the searched filename.
- These parameters will be dynamically substituted at runtime with values
- which will depend on currently selected item(s).
+ These parameters will be dynamically substituted at runtime with
+ values which will depend on currently selected item(s).
</para>
</tip>
</sect3>
@@ -941,8 +1021,10 @@
name is registered on the D-Bus system at runtime.
</para>
<para>
+ <!-- i18n: "Environment" is a UI label -->
Click on the <guilabel>Environment</guilabel> tab to show the page
which will permit you to configure your environment-based conditions,
+ <!-- i18n: "Execution environment" is a UI label -->
and focus on <guilabel>Execution environment</guilabel> frame.
</para>
<para>
@@ -957,8 +1039,8 @@
<tip>
<para>
You may embed some parameters in the searched name.
- These parameters will be dynamically substituted at runtime with values
- which will depend on currently selected item(s).
+ These parameters will be dynamically substituted at runtime with
+ values which will depend on currently selected item(s).
</para>
</tip>
</sect3>
@@ -967,21 +1049,26 @@
<title>Customized condition</title>
<para>
You may define that your action will only appear if some given
+ <!-- i18n: "true" is a literal value, not translatable -->
command outputs a <literal>true</literal> string on its standard
output.
</para>
<para>
+ <!-- i18n: "Environment" is a UI label -->
Click on the <guilabel>Environment</guilabel> tab to show the page
which will permit you to configure your environment-based conditions,
+ <!-- i18n: "Execution environment" is a UI label -->
and focus on <guilabel>Execution environment</guilabel> frame.
</para>
<para>
This lets you define your own customized condition filter,
by writing a small script which outputs, or not, the
+ <!-- i18n: "true" is a literal value, not translatable -->
<literal>true</literal> string on stdout when it is ran.
</para>
<para>
To define the command, enter it in the
+ <!-- i18n: "true" is a literal value, not translatable -->
<guilabel>Appears if the command outputs "true"</guilabel>
entry box.
</para>
@@ -991,9 +1078,10 @@
</para>
<tip>
<para>
- You may embed some parameters in the executed filename or its options.
- These parameters will be dynamically substituted at runtime with values
- which will depend on currently selected item(s).
+ You may embed some parameters in the executed filename or its
+ options. These parameters will be dynamically substituted at
+ runtime with values which will depend on currently selected
+ item(s).
</para>
</tip>
</sect3>
@@ -1005,13 +1093,16 @@
binary is currently running.
</para>
<para>
+ <!-- i18n: "Environment" is a UI label -->
Click on the <guilabel>Environment</guilabel> tab to show the page
which will permit you to configure your environment-based conditions,
+ <!-- i18n: "Execution environment" is a UI label -->
and focus on <guilabel>Execution environment</guilabel> frame.
</para>
<para>
To define the binary, enter its name in the
<guilabel>Appears if the binary is running</guilabel>
+ <!-- i18n: "Browse" is a UI (button) label -->
entry box, or click on <guibutton>Browse</guibutton> to select
a file on the file system.
</para>
@@ -1029,8 +1120,8 @@
<tip>
<para>
You may embed some parameters in the searched name.
- These parameters will be dynamically substituted at runtime with values
- which will depend on currently selected item(s).
+ These parameters will be dynamically substituted at runtime
+ with values which will depend on currently selected item(s).
</para>
</tip>
</sect3>
diff --git a/docs/nact/C/nact-edit.xml b/docs/nact/C/nact-edit.xml
index 054384f..0e9bfeb 100644
--- a/docs/nact/C/nact-edit.xml
+++ b/docs/nact/C/nact-edit.xml
@@ -13,7 +13,7 @@
Be warned that selecting and deleting all profiles of an action
leaves it without any profile, so in an invalid state.
The name of the action will be written in red (because it is
- invalid) italic (because it has been modified) characters.
+ invalid) and italic (because it has been modified) characters.
</para>
</sect3>
@@ -22,6 +22,7 @@
<para>
Multiple selection is possible in &appname;.
You can extend the current selection
+ <!-- i18n: "Ctrl" and "Shit" are key names -->
by pressing <keycap>Ctrl</keycap> or <keycap>Shift</keycap>
while selecting an item to add to the selection.
</para>
diff --git a/docs/nact/C/nact-execution.xml b/docs/nact/C/nact-execution.xml
index 7dddcea..828d31b 100644
--- a/docs/nact/C/nact-execution.xml
+++ b/docs/nact/C/nact-execution.xml
@@ -8,6 +8,7 @@
</para>
<para>
As we have already seen, the command to be executed is configured
+ <!-- i18n: "Command" is a UI label -->
in the <guilabel>Command</guilabel> page.
</para>
<para>
@@ -19,7 +20,10 @@
<sect3 id="usage-execution-parameters">
<title>Available parameters</title>
<para>
- In the <guilabel>Command</guilabel> page, click on <guilabel>Legend</guilabel>
+ <!-- i18n: "Command" is a UI label -->
+ In the <guilabel>Command</guilabel> page,
+ <!-- i18n: "Legend" is a UI label -->
+ click on <guilabel>Legend</guilabel>
button to see the list of available parameters.
</para>
<figure id="nact-FIG-legend">
@@ -40,23 +44,27 @@
</figure>
<tip>
<para>
+ <!-- i18n: "Legend" is a UI label -->
The <guibutton>Legend</guibutton> button has a toggling action:
+ <!-- i18n: "Parameter Legend" is a UI label -->
click once to display the <guilabel>Parameter Legend</guilabel>
dialog box; click a second time to hide it.
</para>
</tip>
<note>
<para>
- The word «sp;<guilabel>first</guilabel>&spraquo; may be misleading
- as it only refers to the list of selected items internally provided by
- the file manager to the &prodname; plugin.
+ <!-- i18n: "first" is a UI label -->
+ The word «sp;<guilabel>first</guilabel>&spraquo; may be
+ misleading as it only refers to the list of selected items
+ internally provided by the file manager to the &prodname; plugin.
</para>
<para>
- In particular, it has <emphasis>nothing to do</emphasis> with the
- visual selection you may
- have done in the file manager window. And, in fact, which is the
- «sp;<guilabel>first</guilabel>&spraquo; selected item in a
- multiple selection is absolutely undefined and rather unpredictable.
+ In particular, it has <emphasis>nothing to do</emphasis> with
+ the visual selection you may have done in the file manager window.
+ <!-- i18n: "first" is a UI label -->
+ And, in fact, which is the «sp;<guilabel>first</guilabel>&spraquo;
+ selected item in a multiple selection is absolutely undefined
+ and rather unpredictable.
</para>
</note>
</sect3>
@@ -67,8 +75,11 @@
Your action may be executed in a particular working directory.
</para>
<para>
+ <!-- i18n: "Command" is a UI label -->
You may specify it in the <guilabel>Command</guilabel> tab, in the
+ <!-- i18n: "Working directory" is a UI label -->
<guilabel>Working directory</guilabel> entry box, or by clicking
+ <!-- i18n: "Browse" is a UI (button) label -->
on <guibutton>Browse</guibutton> to select a folder on the
filesystem.
</para>
@@ -89,26 +100,29 @@
</screenshot>
</figure>
<para>
- The working directory defaults to <literal>%d</literal>, which runs
- the command in the base directory of the (first) selected item.
+ The working directory defaults to <literal>%d</literal>, which
+ runs the command in the base directory of the (first) selected
+ item.
</para>
<para>
In the particular case of the <literal>%d</literal> parameter,
+ <!-- i18n: "first" is a UI label -->
the «sp;<guilabel>first</guilabel>&spraquo; selected item
- is not very important because it is very likely that all selected items
- are located in the same base directory.
+ is not very important because it is very likely that all selected
+ items are located in the same base directory.
</para>
</sect3>
<sect3 id="usage-execution-how">
<title>How should the action be executed ?</title>
<para>
- Apart from configuring the conditions, the selection must be met in
- order your action be displayed in file manager menus, &prodname;
+ Apart from configuring the conditions, the selection must be met
+ in order your action be displayed in file manager menus, &prodname;
allows you to configure how exactly your command will be
executed.
</para>
<para>
+ <!-- i18n: "Execution" is a UI label -->
Click on the <guilabel>Execution</guilabel> tab to show the page
which configures the execution of your command.
</para>
@@ -228,8 +242,10 @@
</figure>
<para>
If the execution mode of the command is <literal>Normal</literal>,
+ <!-- i18n: "remove" is a X literal, do not translate -->
and if you know that the application will send a <literal>remove</literal>
message with the <envar>DESKTOP_STARTUP_ID</envar> environment variable set,
+ <!-- i18n: "Startup notify" is a UI label -->
then check the <guilabel>Startup notify</guilabel> checkbox.
</para>
<para>
@@ -244,9 +260,10 @@
<title>Window class</title>
<para>
If the execution mode of the command is <literal>Normal</literal>,
- and if you know that the application will map at least one window with a
- given class name,
- then enter that name into the <guilabel>Startup Window Manager class</guilabel>
+ and if you know that the application will map at least one window
+ with a given class name, then enter that name into the
+ <!-- i18n: "Startup Window Manager class" is a UI label -->
+ <guilabel>Startup Window Manager class</guilabel>
entry box.
</para>
<para>
@@ -276,29 +293,30 @@
</screenshot>
</figure>
<para>
- Enter in the <guilabel>Execute as user</guilabel> entry box the username
- or the <acronym>UID</acronym> of the user your command will be run as.
+ Enter in the <guilabel>Execute as user</guilabel> entry box the
+ username or the <acronym>UID</acronym> of the user your command
+ will be run as.
</para>
<para>
- If you do not enter anything in this field, then the command will be
- executed as the current user.
+ If you do not enter anything in this field, then the command will
+ be executed as the current user.
</para>
</sect4>
<sect4 id="usage-execution-how-singular">
<title>Multiple executions</title>
<para>
- You may want your command to be executed once, providing it the list of
- selected items as argument.
+ You may want your command to be executed once, providing it the
+ list of selected items as argument.
</para>
<para>
- Or you may prefer your command to be repeated for each selected item,
- providing a different item as argument for each execution.
+ Or you may prefer your command to be repeated for each selected
+ item, providing a different item as argument for each execution.
</para>
<para>
Actually, &prodname; automatically handles these two behaviors,
- depending of the form and the order of the parameters in the command
- arguments.
+ depending of the form and the order of the parameters in the
+ command arguments.
</para>
<para>
Though some parameters are not depending on the count of the
@@ -323,7 +341,8 @@
</itemizedlist>
<para>
When the selection is empty or contains only one element,
- and from this topic point of view, these two forms are exactly equivalent.
+ and from this topic point of view, these two forms are exactly
+ equivalent.
</para>
<para>
When the selection contains more than one item:
@@ -332,16 +351,17 @@
<listitem>
<para>
if the first relevant parameter is of a singular form,
- then &prodname; will consider that the command is only able to deal
- with one item at a time, and thus that it has to be ran one time for
- each selected item;
+ then &prodname; will consider that the command is only able
+ to deal with one item at a time, and thus that it has to be
+ ran one time for each selected item;
</para>
</listitem>
<listitem>
<para>
- contrarily, if the first relevant parameter found is of the plural form,
- then &prodname; will consider that the command is able to deal with a
- list of items, and thus the command will be executed only once;
+ contrarily, if the first relevant parameter found is of the
+ plural form, then &prodname; will consider that the command
+ is able to deal with a list of items, and thus the command
+ will be executed only once;
</para>
</listitem>
<listitem>
@@ -597,11 +617,12 @@
<member><command>echo pierre paul jacques pierre</command></member>
</simplelist>
<para>
- This is because the first <emphasis>relevant</emphasis> parameter here
- is <literal>%B</literal>. The command is then run only once, replacing
- <literal>%B</literal> with the space-separated list of basenames. As
- the command is only run once, the <literal>%b</literal> is substituted
- only once with the (first) basename.
+ This is because the first <emphasis>relevant</emphasis>
+ parameter here is <literal>%B</literal>. The command is then
+ run only once, replacing <literal>%B</literal> with the
+ space-separated list of basenames. As the command is only run
+ once, the <literal>%b</literal> is substituted only once with
+ the (first) basename.
</para>
</example>
</sect4>
diff --git a/docs/nact/C/nact-menus.xml b/docs/nact/C/nact-menus.xml
index da60c5e..5290cad 100644
--- a/docs/nact/C/nact-menus.xml
+++ b/docs/nact/C/nact-menus.xml
@@ -1,19 +1,22 @@
<sect2 id="usage-menus">
<title>Organizing actions in menus</title>
<para>
- As your list of actions will grow, you most probably will want to organize
- them into menus, submenus, and so on.
+ As your list of actions will grow, you most probably will want to
+ organize them into menus, submenus, and so on.
</para>
<para>
In order to create a new menu, choose
<menuchoice>
+ <!-- i18n: "File" is a menu item -->
<guimenu>File</guimenu>
+ <!-- i18n: "New menu" is a menu item -->
<guimenuitem>New menu</guimenuitem>
</menuchoice>.
</para>
<para>
- A menu may be created anywhere in the list of your actions, but inside
- of an action (<abbrev>i.e.</abbrev> not between two profiles of an action).
+ A menu may be created anywhere in the list of your actions, but
+ inside of an action (<abbrev>i.e.</abbrev> not between two profiles
+ of an action).
</para>
<para>
As an action, the exact place where a new menu will be inserted
@@ -26,10 +29,12 @@
</term>
<listitem>
<para>
- The new menu is inserted just before the current action or menu.
+ The new menu is inserted just before the current action or
+ menu.
</para>
<para>
- This place will not change when you later modify the label of the menu.
+ This place will not change when you later modify the label of
+ the menu.
</para>
</listitem>
</varlistentry>
@@ -39,21 +44,23 @@
</term>
<listitem>
<para>
- The new menu is inserted at the correct place, regarding the default
- «sp;<literal>New Nautilus menu</literal>&spraquo; label.
+ The new menu is inserted at the correct place, regarding the
+ <!-- i18n: "New Nautilus menu" is a UI label -->
+ default «sp;<literal>New Nautilus menu</literal>&spraquo;
+ label.
</para>
<para>
- This place will be automatically changed, each time you modify the
- label of the menu.
+ This place will be automatically changed, each time you modify
+ the label of the menu.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
- As an action, too, a menu requires a label, and may have an icon and a
- tooltip. Also, you may define some conditions in order your menu be
- candidate to be displayed in &nautilus; context menu. If the defined
- conditions are not met at runtime, then your whole menu, including
- its submenus, its actions and so on, will not be displayed.
+ As an action, too, a menu requires a label, and may have an icon and
+ a tooltip. Also, you may define some conditions in order your menu
+ be candidate to be displayed in &nautilus; context menu. If the
+ defined conditions are not met at runtime, then your whole menu,
+ including its submenus, its actions and so on, will not be displayed.
</para>
</sect2>
diff --git a/docs/nact/C/nact-misc.xml b/docs/nact/C/nact-misc.xml
index 6eb3238..23bd8db 100644
--- a/docs/nact/C/nact-misc.xml
+++ b/docs/nact/C/nact-misc.xml
@@ -1,8 +1,11 @@
<para>
- The new action is also displayed in red color in the items list.
- Red color is used as an indicator that the item
- is invalid, that is that the item cannot be candidate to be displayed in a
- &nautilus; context menu because some of its informations are missing or erroneous.
- Here, and though this newly inserted action has some suitable defaults, it lacks a
- command to be executed to be considered valid by &appname;
+ The new action is also displayed in red color in the items
+ list.
+ Red color is used as an indicator that the item is invalid,
+ that is that the item cannot be candidate to be displayed in
+ a &nautilus; context menu because some of its informations are
+ missing or erroneous.
+ Here, and though this newly inserted action has some suitable
+ defaults, it lacks a command to be executed to be considered
+ valid by &appname;
</para>
diff --git a/docs/nact/C/nact-prefs.xml b/docs/nact/C/nact-prefs.xml
index ff74927..93dd06b 100644
--- a/docs/nact/C/nact-prefs.xml
+++ b/docs/nact/C/nact-prefs.xml
@@ -3,7 +3,9 @@
<para>
Choose
<menuchoice>
+ <!-- i18n: "Edit" is a menu item -->
<guimenu>Edit</guimenu>
+ <!-- i18n: "Preferences" is a menu item -->
<guimenuitem>Preferences</guimenuitem>
</menuchoice>
to access to the configuration of your preferences.
diff --git a/docs/nact/C/nact-profiles.xml b/docs/nact/C/nact-profiles.xml
index 00d4056..c23c973 100644
--- a/docs/nact/C/nact-profiles.xml
+++ b/docs/nact/C/nact-profiles.xml
@@ -8,7 +8,8 @@
<example>
<title>Open a terminal here</title>
<para>
- Say you have an action which opens a terminal in the current location.
+ Say you have an action which opens a terminal in the current
+ location.
</para>
<para>
You have configured it to open your preferred terminal in the
@@ -36,7 +37,9 @@
To create a new profile, first select the action in the items list,
then choose
<menuchoice>
+ <!-- i18n: "File" is a menu item -->
<guisubmenu>File</guisubmenu>
+ <!-- i18n: "New profile" is a menu item -->
<guimenuitem>New profile</guimenuitem>
</menuchoice>.
</para>
@@ -55,8 +58,8 @@
set on your action.
</para>
<para>
- If these conditions (the action-conditions) are met, then &prodname;
- will examine in order each profile.
+ If these conditions (the action-conditions) are met, then
+ &prodname; will examine in order each profile.
</para>
<para>
If the conditions defined in a profile are met, then this profile
@@ -68,13 +71,13 @@
manager context menu.
</para>
<para>
- Profiles of an action are ordered, and they are examined in that order
- at runtime. The first profile whose conditions are met will be validated,
- and made selectable in the &nautilus; context menu.
+ Profiles of an action are ordered, and they are examined in that
+ order at runtime. The first profile whose conditions are met will
+ be validated, and made selectable in the &nautilus; context menu.
</para>
<para>
- So, ordering of the profiles may be important for your action: the
- first valid profile found is the only one selected.
+ So, ordering of the profiles may be important for your action:
+ the first valid profile found is the only one selected.
</para>
<para>
You may order your profiles inside an action in two ways.
diff --git a/docs/nact/C/nact-properties.xml b/docs/nact/C/nact-properties.xml
index e05e49f..2f7f72f 100644
--- a/docs/nact/C/nact-properties.xml
+++ b/docs/nact/C/nact-properties.xml
@@ -1,7 +1,7 @@
<sect2 id="usage-properties">
<title>Accessing and editing item properties</title>
<para>
- An item has bot editable and read-only properties
+ An item has both editable and read-only properties.
</para>
<figure id="nact-FIG-prefs-runtime">
diff --git a/docs/nact/C/nact-save.xml b/docs/nact/C/nact-save.xml
index f9150fb..7cf2220 100644
--- a/docs/nact/C/nact-save.xml
+++ b/docs/nact/C/nact-save.xml
@@ -5,20 +5,25 @@
<menuchoice>
<shortcut>
<keycombo>
+ <!-- i18n: "Ctrl" is a key name -->
<keycap>Ctrl</keycap>
<keycap>S</keycap>
</keycombo>
</shortcut>
+ <!-- i18n: "File" is a menu item -->
<guimenu>File</guimenu>
+ <!-- i18n: "Save" is a menu item -->
<guisubmenu>Save</guisubmenu>
</menuchoice>.
</para>
<para>
All your pending modifications will be saved.
- New items will be created by the first available writable I/O provider.
+ New items will be created by the first available writable I/O
+ provider.
</para>
<para>
&prodname; also has an Auto-save feature which is configurable in
+ <!-- i18n: "Preferences" is a menu item -->
<guimenuitem>Preferences</guimenuitem> dialog box.
</para>
</sect2>
diff --git a/docs/nact/C/nact-sorting.xml b/docs/nact/C/nact-sorting.xml
index dc0e2e2..1a820b5 100644
--- a/docs/nact/C/nact-sorting.xml
+++ b/docs/nact/C/nact-sorting.xml
@@ -1,8 +1,10 @@
<sect2 id="usage-sorting">
<title>Sorting the items list</title>
<para>
- Your actions and menus will be displayed in file manager context menus
- in the same order that they are listed in the <guilabel>Items list</guilabel>,
+ Your actions and menus will be displayed in file manager context
+ menus in the same order that they are listed in the
+ <!-- i18n: "Items list" is a UI label -->
+ <guilabel>Items list</guilabel>,
on the left pane of the main &appname; window.
</para>
<para>
@@ -11,8 +13,8 @@
<itemizedlist>
<listitem>
<para>
- sort your actions and menus in ascending or descending alphabetical
- order of their label,
+ sort your actions and menus in ascending or descending
+ alphabetical order of their label,
</para>
</listitem>
<listitem>
@@ -26,8 +28,8 @@
<sect3 id="usage-sorting-alpha">
<title>Alphabetically sorting your actions and menus</title>
<para>
- In these modes, actions and menus are sorted depending of their label,
- inside of their parent.
+ In these modes, actions and menus are sorted depending of their
+ label, inside of their parent.
</para>
<figure id="nact-FIG-sort-buttons">
<title>Sort buttons in the main window</title>
diff --git a/docs/nact/C/nact-starting.xml b/docs/nact/C/nact-starting.xml
index 362f256..d2ba896 100644
--- a/docs/nact/C/nact-starting.xml
+++ b/docs/nact/C/nact-starting.xml
@@ -27,6 +27,7 @@
<command><filename>nautilus-actions-config-tool</filename></command>
</para>
<para>
+ <!-- i18n: "Return" is a key name -->
then press <keycap>Return</keycap>.
</para>
<tip>
@@ -40,6 +41,7 @@
</command>
</para>
<para>
+ <!-- i18n: "Return" is a key name -->
then press <keycap>Return</keycap>.
</para>
</tip>
@@ -64,8 +66,8 @@
<phrase>
Shows &appname; main window.
Contains menubar, toolbar, display area,
- an empty items list in the left, several disabled properties tabs,
- and statusbar.
+ an empty items list in the left, several disabled
+ properties tabs, and statusbar.
</phrase>
</textobject>
<caption>
@@ -229,8 +231,8 @@
<term>Toolbar.</term>
<listitem>
<para>
- Several toolbars may be displayed below the menubar, depending of
- your choices in the
+ Several toolbars may be displayed below the menubar,
+ depending of your choices in the
<menuchoice>
<guimenu>View</guimenu>
<guimenuitem>Toolbars</guimenuitem>
@@ -243,12 +245,13 @@
<listitem>
<para>
The list on the left of the main window contains all items,
- whether they are actions or menus, currently available for edition in
- &appname;.
+ whether they are actions or menus, currently available for
+ edition in &appname;.
</para>
<para>
- Items may be sorted in ascending or descending alphabetical order, or
- not sorted at all, being directly organized and managed by the user.
+ Items may be sorted in ascending or descending alphabetical
+ order, or not sorted at all, being directly organized and
+ managed by the user.
</para>
<para>
Invalid items are displayed in red color.
@@ -270,8 +273,9 @@
<term>Properties tabs.</term>
<listitem>
<para>
- The right part of the main window displays all is needed to define
- how, when and where actions and menus should be displayed.
+ The right part of the main window displays all is needed
+ to define how, when and where actions and menus should be
+ displayed.
</para>
<variablelist>
<varlistentry>
@@ -280,8 +284,8 @@
</term>
<listitem>
<para>
- Define in which &nautilus; menus the item should appear, and
- how it will be displayed.
+ Define in which &nautilus; menus the item should
+ appear, and how it will be displayed.
</para>
</listitem>
</varlistentry>
@@ -312,8 +316,9 @@
</term>
<listitem>
<para>
- Define the basename filters the &nautilus; selection must satisfy
- in order the action or menu be candidate for display.
+ Define the basename filters the &nautilus; selection
+ must satisfy in order the action or menu be candidate
+ for display.
</para>
</listitem>
</varlistentry>
@@ -323,8 +328,9 @@
</term>
<listitem>
<para>
- Define the mimetype filters the &nautilus; selection must satisfy
- in order the action or menu be candidate for display.
+ Define the mimetype filters the &nautilus; selection
+ must satisfy in order the action or menu be candidate
+ for display.
</para>
</listitem>
</varlistentry>
@@ -334,8 +340,9 @@
</term>
<listitem>
<para>
- Define the folder filters the &nautilus; selection must satisfy
- in order the action or menu be candidate for display.
+ Define the folder filters the &nautilus; selection
+ must satisfy in order the action or menu be candidate
+ for display.
</para>
</listitem>
</varlistentry>
@@ -345,8 +352,9 @@
</term>
<listitem>
<para>
- Define the scheme filters the &nautilus; selection must satisfy
- in order the action or menu be candidate for display.
+ Define the scheme filters the &nautilus; selection
+ must satisfy in order the action or menu be candidate
+ for display.
</para>
</listitem>
</varlistentry>
@@ -356,8 +364,9 @@
</term>
<listitem>
<para>
- Define the capability filters the &nautilus; selection must satisfy
- in order the action or menu be candidate for display.
+ Define the capability filters the &nautilus; selection
+ must satisfy in order the action or menu be candidate
+ for display.
</para>
</listitem>
</varlistentry>
@@ -367,8 +376,9 @@
</term>
<listitem>
<para>
- Define some environment conditions the &nautilus; selection must satisfy
- in order the action or menu be candidate for display.
+ Define some environment conditions the &nautilus;
+ selection must satisfy in order the action or menu
+ be candidate for display.
</para>
</listitem>
</varlistentry>
@@ -393,10 +403,12 @@
currently selected row in the items list.
</para>
<para>
- When no relevant information is to be displayed, the statusbar
- displays the count of loaded menus, actions and profiles.
+ When no relevant information is to be displayed, the
+ statusbar displays the count of loaded menus, actions
+ and profiles.
</para>
<para>
+ <!-- i18n: "read-only" may be translated -->
The «sp;read-only&spraquo; icon
<inlinegraphic fileref="figures/read-only.png" />
is displayed in
@@ -410,8 +422,8 @@
<sect2 id="getting-started-first-action">
<title>Creating your first action</title>
<para>
- In this example, we are going to create an action which displays some
- pretty informations about the current selection.
+ In this example, we are going to create an action which displays
+ some pretty informations about the current selection.
</para>
<formalpara>
<title>Checking for prerequisites</title>
@@ -425,8 +437,8 @@
</para>
<para>
You should check that this program
- is installed on your system, by example by typing the following command
- in a terminal:
+ is installed on your system, by example by typing the following
+ command in a terminal:
</para>
<para>
<command>
@@ -479,10 +491,13 @@
</screenshot>
</figure>
<para>
- In the <guilabel>Items list</guilabel>, the new action is displayed in italic characters.
+ <!-- i18n: "Items list" is a UI label -->
+ In the <guilabel>Items list</guilabel>, the new action is
+ displayed in italic characters.
</para>
<para>
- Italics are used as a reminder that the item has not yet been saved.
+ Italics are used as a reminder that the item has not yet been
+ saved.
</para>
<para>
As another reminder that there is some pending modifications,
@@ -492,35 +507,41 @@
<formalpara>
<title>Qualifying your new action</title>
<para>
- It merely consists of choosing how your action will be displayed
- in the file manager context menu.
+ It merely consists of choosing how your action will be
+ displayed in the file manager context menu.
</para>
</formalpara>
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "My first action" is a user entry -->
Enter <userinput>My first action</userinput>
+ <!-- i18n: "Context label" is a UI label -->
in the <guilabel>Context label</guilabel> entry box.
</para>
<para>
- The <guilabel>Context label</guilabel> entry box contains the label
- of the action as you want it to be displayed in the file manager
- context menu.
+ <!-- i18n: "Context label" is a UI label -->
+ The <guilabel>Context label</guilabel> entry box contains
+ the label of the action as you want it to be displayed in
+ the file manager context menu.
</para>
<para>
- The label is a mandatory property of your action. If it happens
- to be empty, then your action will be considered as invalid by
- &prodname;: it will be displayed in red in <guilabel>Items list</guilabel>
- and will never be candidate to be displayed in the
- file manager context menus.
+ The label is a mandatory property of your action. If it
+ happens to be empty, then your action will be considered as
+ invalid by &prodname;: it will be displayed in red in
+ <!-- i18n: "Items list" is a UI label -->
+ <guilabel>Items list</guilabel> and will never be candidate
+ to be displayed in the file manager context menus.
</para>
</listitem>
<listitem>
<para>
Enter <userinput>This will execute an action with some parameters</userinput>
+ <!-- i18n: "Tooltip" is a UI label -->
in the <guilabel>Tooltip</guilabel> entry box.
</para>
<para>
+ <!-- i18n: "Tooltip" is a UI label -->
The <guilabel>Tooltip</guilabel> entry box contains the text
you want to be displayed as a short help to your action.
</para>
@@ -528,20 +549,25 @@
<listitem>
<para>
Select <inlinegraphic fileref="figures/stock-icon-about.png" />
+ <!-- i18n: "Icon" is a UI label -->
in the <guilabel>Icon</guilabel> drop-down list.
</para>
<para>
- The <guilabel>Icon</guilabel> selection defines the icon which will
- be associated with your action in file manager context menus and in
- the toolbar.
+ <!-- i18n: "Icon" is a UI label -->
+ The <guilabel>Icon</guilabel> selection defines the icon
+ which will be associated with your action in file manager
+ context menus and in the toolbar.
</para>
<para>
- You have two ways of choosing the icon associated to your action:
+ You have two ways of choosing the icon associated to your
+ action:
</para>
<itemizedlist>
<listitem>
<para>
- Click on the <guilabel>Icon</guilabel> drop-down list to select an icon.
+ <!-- i18n: "Icon" is a UI label -->
+ Click on the <guilabel>Icon</guilabel> drop-down list
+ to select an icon.
</para>
</listitem>
<listitem>
@@ -562,6 +588,7 @@
</para>
</formalpara>
<para>
+ <!-- i18n: "Command" is a UI label -->
Click on the <guilabel>Command</guilabel> tab to show the page
which will permit you to enter the command.
</para>
@@ -589,13 +616,15 @@
<itemizedlist>
<listitem>
<para>
- Enter <userinput>zenity</userinput> in the <guilabel>Path</guilabel>
- entry box.
+ Enter <userinput>zenity</userinput> in the
+ <!-- i18n: "Path" is a UI label -->
+ <guilabel>Path</guilabel> entry box.
</para>
<para>
- The <guilabel>Path</guilabel> entry box defines the command which
- will be executed when you will select your action in the file manager
- context menu.
+ <!-- i18n: "Path" is a UI label -->
+ The <guilabel>Path</guilabel> entry box defines the command
+ which will be executed when you will select your action in
+ the file manager context menu.
</para>
<para>
You have two ways of defining the command to be executed:
@@ -603,6 +632,7 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Path" is a UI label -->
Enter it in the <guilabel>Path</guilabel> entry box.
</para>
</listitem>
@@ -621,21 +651,27 @@
</listitem>
<listitem>
<para>
+ <!-- i18n: only "selected item(s)" is translatable -->
Enter <userinput>--info --text='%c selected item(s): %U'</userinput>
+ <!-- i18n: "Parameters" is a UI label -->
in the <guilabel>Parameters</guilabel>
entry box.
</para>
<para>
- The <guilabel>Parameters</guilabel> contains the arguments which will
- be passed to your command when it will be executed. These arguments may
- embed parameters which will be expanded at runtime.
+ <!-- i18n: "Parameters" is a UI label -->
+ The <guilabel>Parameters</guilabel> contains the arguments
+ which will be passed to your command when it will be executed.
+ These arguments may embed parameters which will be expanded
+ at runtime.
</para>
<para>
+ <!-- i18n: "Path" and "Parameters" are UI labels -->
If both <guilabel>Path</guilabel> and <guilabel>Parameters</guilabel>
- are empty, then this action will be considered as invalid: it will be
- displayed in red in <guilabel>Items list</guilabel> and will be
- never be candidate to be displayed in the
- file manager context menus.
+ are empty, then this action will be considered as invalid:
+ <!-- i18n: "Items list" is a UI label -->
+ it will be displayed in red in <guilabel>Items list</guilabel>
+ and will never be candidate to be displayed in the file
+ manager context menus.
</para>
</listitem>
</itemizedlist>
diff --git a/docs/nact/C/nact-where.xml b/docs/nact/C/nact-where.xml
index 2847311..4b94df9 100644
--- a/docs/nact/C/nact-where.xml
+++ b/docs/nact/C/nact-where.xml
@@ -22,6 +22,7 @@
selected (or not).
</para>
<para>
+ <!-- i18n: "Action" is a UI label -->
Click on the <guilabel>Action</guilabel> tab to show the page
which will permit you to configure the locations your action
targets.
@@ -103,17 +104,20 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Context label" is a UI label -->
the <guilabel>Context label</guilabel> as a label,
</para>
</listitem>
<listitem>
<para>
+ <!-- i18n: "Icon" is a UI label -->
the <guilabel>Icon</guilabel>,
</para>
</listitem>
<listitem>
<para>
these two properties being associated with the
+ <!-- i18n: "Tooltip" is a UI label -->
<guilabel>Tooltip</guilabel>.
</para>
</listitem>
@@ -127,9 +131,9 @@
</note>
<tip>
<para>
- You may embed some parameters in the label, the icon name or the tooltip.
- These parameters will be dynamically substituted at runtime with values
- which will depend on currently selected item(s).
+ You may embed some parameters in the label, the icon name or the
+ tooltip. These parameters will be dynamically substituted at runtime
+ with values which will depend on currently selected item(s).
</para>
</tip>
@@ -142,17 +146,20 @@
<itemizedlist>
<listitem>
<para>
+ <!-- i18n: "Toolbar label" is a UI label -->
the <guilabel>Toolbar label</guilabel> as a label,
</para>
</listitem>
<listitem>
<para>
+ <!-- i18n: "Icon" is a UI label -->
the <guilabel>Icon</guilabel>,
</para>
</listitem>
<listitem>
<para>
these two properties being associated with the
+ <!-- i18n: "Tooltip" is a UI label -->
<guilabel>Tooltip</guilabel>.
</para>
</listitem>
@@ -170,14 +177,16 @@
those used in menus. By unchecking the
<guilabel>Use same label for icon in the toolbar</guilabel>
checkbox you can define a label specific to the
- toolbar, which is usually shorter that those defined for the menus.
+ toolbar, which is usually shorter that those defined for the
+ menus.
</para>
</tip>
<tip>
<para>
- You may embed some parameters in the toolbar label, the icon name or the tooltip.
- These parameters will be dynamically substituted at runtime with values
- which will depend on currently selected item(s).
+ You may embed some parameters in the toolbar label, the icon
+ name or the tooltip. These parameters will be dynamically
+ substituted at runtime with values which will depend on currently
+ selected item(s).
</para>
</tip>
@@ -193,8 +202,8 @@
<title>Defining no target at all</title>
<para>
If no target is defined,
- <abbrev>i.e.</abbrev> if the three checkboxes are unchecked, then your action
- will never be displayed.
+ <abbrev>i.e.</abbrev> if the three checkboxes are unchecked,
+ then your action will never be displayed.
</para>
</formalpara>
</sect3>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
