From acba359ada7fce37efa0ad7eec8ce0754c06f623 Mon Sep 17 00:00:00 2001 From: Pierre Wieser Date: Wed, 10 Oct 2012 21:30:58 +0200 Subject: [PATCH] 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 | 19 +-- 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, 432 insertions(+), 252 deletions(-) rewrite docs/nact/C/nact-misc.xml (68%) diff --git a/docs/nact/C/nact-conditions.xml b/docs/nact/C/nact-conditions.xml index e83efefd..e0a3ee43 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. + Click on the Basenames tab to show the page which will permit you to configure your basename-based conditions. @@ -47,11 +48,11 @@ 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. If at least one element of the selection does not match all the defined @@ -74,6 +75,7 @@ + Press Insert or click on button to insert a new condition filter @@ -81,7 +83,8 @@ - Edit the newly inserted condition filter to the basename you want match. + Edit the newly inserted condition filter to the basename you + want match. @@ -98,21 +101,26 @@ or a &must_not_match; condition. + Click on the Must match one of or - Must not match any of radio button in the same - row to set the corresponding condition. + + Must not match any of radio button in the + same row to set the corresponding condition. Depending of your target operating system, make sure that the + Match case checkbox is activated (or not). When activated, all filters are considered as case sensitive, + which means that /my/file filename is + considered distinct from /My/File one. @@ -122,7 +130,9 @@ When deactivated, filters are considered as case insensitive, + which means that /my/file and + /My/File filenames are considered the same name. @@ -134,12 +144,14 @@ Removing a defined basename-based condition is as simple as selecting + it, and pressing Del (or clicking on button). By default, the basename-based condition is just one + «sp;must match one of *&spraquo; condition. As all basenames always match the &asterisk; condition, this just means that basename-based conditions are not @@ -151,11 +163,13 @@ Mimetype-based conditions 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. + Click on the Mimetypes tab to show the page which will permit you to configure your mimetype-based conditions. @@ -178,22 +192,24 @@ 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. - 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. - 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 + + «sp;inode/directory&spraquo; mimetype. Defining a new mimetype-based condition involves two steps. @@ -206,6 +222,7 @@ + Press Insert or click on button to insert a new condition filter @@ -213,15 +230,19 @@ - Edit the newly inserted condition filter to the mimetype you want match. + Edit the newly inserted condition filter to the mimetype + you want match. - A mimetype must be defined as a group/subgroup + A mimetype must be defined as a + + group/subgroup expression. - The &asterisk; wildcard is supported only in some situations: + The &asterisk; wildcard is supported only in some + situations: @@ -233,12 +254,15 @@ + A group/* string + matches all subgroups of group mimetype. + The */subgroup string is not accepted as a valid wildcard. @@ -250,23 +274,28 @@ - Indicates whether this a &must_match; or a &must_not_match; condition. + Indicates whether this a &must_match; or a &must_not_match; + condition. + Click on the Must match one of or - Must not match any of radio button in the same - row to set the corresponding condition. + + Must not match any of radio button in the + same row to set the corresponding condition. - Removing a defined mimetype-based condition is as simple as selecting - it, and pressing Del (or clicking on + Removing a defined mimetype-based condition is as simple as + + selecting it, and pressing Del (or clicking on button). By default, the mimetype-based condition is just one + «sp;must match one of */*&spraquo; condition. As all mimetypes always match the «sp;*/*&spraquo;, this just means that mimetypes are not considered as relevant @@ -277,6 +306,7 @@ + all/all @@ -287,6 +317,7 @@ + all/allfiles @@ -297,6 +328,7 @@ + inode/directory @@ -312,12 +344,12 @@ Folder-based conditions - 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. 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. + Click on the Folders tab to show the page which will permit you to configure your folder-based conditions. @@ -347,11 +380,11 @@ 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. If at least one element of the selection does not match all the @@ -376,6 +409,7 @@ + Press Insert or click on button to insert a new condition filter @@ -383,7 +417,8 @@ - Edit the newly inserted condition filter to the folder you want match. + Edit the newly inserted condition filter to the folder you + want match. @@ -407,20 +442,24 @@ condition. + Click on the Must match one of or - Must not match any of radio button in the same - row to set the corresponding condition. + + Must not match any of radio button in + the same row to set the corresponding condition. - Removing a defined folder-based condition is as simple as selecting - it, and pressing Del (or clicking on + Removing a defined folder-based condition is as simple as + + selecting it, and pressing Del (or clicking on button). By default, the folder-based condition is just one + «sp;must match one of /&spraquo; condition. As / is always the top of an Unix-like file system, then all selected items always match this condition. @@ -436,13 +475,14 @@ Scheme-base-conditions - 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. + Click on the Schemes tab to show the page which will permit you to configure your scheme-based conditions. @@ -465,21 +505,22 @@ 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. - 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. - 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. Defining a new scheme-based condition involves two steps. @@ -492,6 +533,7 @@ + Press Insert or click on button to insert a new condition filter @@ -499,7 +541,8 @@ - Edit the newly inserted condition filter to the scheme you want match. + Edit the newly inserted condition filter to the scheme you + want match. @@ -511,10 +554,13 @@ Or click on + Common to select a scheme among those predefined in + Edit + Preferences . @@ -535,22 +581,26 @@ - 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. - To select a new scheme, click OK, or - double-click on the desired row. + + To select a new scheme, click OK, + or double-click on the desired row. - Indicates whether this a &must_match; or a &must_not_match; condition. + Indicates whether this a &must_match; or a &must_not_match; + condition. + Click on the Must match one of or + Must not match any of radio button in the same row to set the corresponding condition. @@ -558,12 +608,14 @@ Removing a defined scheme-based condition is as simple as selecting + it, and pressing Del (or clicking on button). By default, the scheme-based condition is just one + «sp;must match one of *&spraquo; condition, which means that schemes are not relevant for this action. @@ -572,9 +624,11 @@ Capability-based conditions - Capabilities are some properties that a file may exhibit to the user. + Capabilities are some properties that a file may exhibit to the + user. + But except for the Local capability, all others depend on the user who executes the command. @@ -584,6 +638,7 @@ the current user. + Click on the Capabilities tab to show the page which will permit you to configure your capability-based conditions. @@ -606,21 +661,23 @@ 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. - 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. - 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. Defining a new capability-based condition involves two steps. @@ -633,18 +690,22 @@ - Press Insert to insert a new condition filter + + Press Insert to insert a new condition + filter. - Edit the newly inserted condition filter to the capability you want match. + Edit the newly inserted condition filter to the capability + you want match. Or click on + to open the Adding a new capability dialog box. @@ -665,12 +726,13 @@ - 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. - To select a new capability, click OK, or - double-click on the desired row. + + To select a new capability, click OK, + or double-click on the desired row. @@ -681,21 +743,24 @@ or a &must_not_match; condition. + Click on the Must match all of or - Must not match any of radio button in the same - row to set the corresponding condition. + + Must not match any of radio button in the + same row to set the corresponding condition. - Removing a defined capability-based condition is as simple as selecting - it, and pressing Del (or clicking on + Removing a defined capability-based condition is as simple as + + selecting it, and pressing Del (or clicking on button). - 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. @@ -711,12 +776,15 @@ If your action consists in displaying the differences between two files, you may define here + «sp;Count = (equal to) 2&spraquo;. - Click on the Environment tab to show the page - which will permit you to configure your environment-based conditions. + + Click on the Environment tab to show the + page which will permit you to configure your environment-based + conditions.
Environment-based conditions @@ -740,6 +808,7 @@
The selection count condition is defined in the + Appears if selection contains frame.
@@ -773,12 +842,16 @@ + Select in the Count drop-down list the operator you want apply to the selection count: + < (strictly less than) + = (equal to) + > (strictly greater than) @@ -790,6 +863,7 @@ The selection count defaults to + «sp;Count > (strictly greater than) 0&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. + Click on the Environment tab to show the page which will permit you to configure your environment-based conditions. The desktop selection is defined in the + Desktop environment frame.
@@ -874,6 +950,7 @@ The targeted desktop environment condition defaults to + «sp;Always appear&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. + Click on the Environment tab to show the page which will permit you to configure your environment-based conditions. The executable found condition is defined in the + Execution environment frame.
@@ -918,6 +997,7 @@ To define the relevant file, enter its full filename in the Appears if the file is executable entry + box, or click on Browse to select a file on the file system. @@ -928,8 +1008,8 @@ 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). @@ -941,8 +1021,10 @@ name is registered on the D-Bus system at runtime. + Click on the Environment tab to show the page which will permit you to configure your environment-based conditions, + and focus on Execution environment frame. @@ -957,8 +1039,8 @@ 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). @@ -967,21 +1049,26 @@ Customized condition You may define that your action will only appear if some given + command outputs a true string on its standard output. + Click on the Environment tab to show the page which will permit you to configure your environment-based conditions, + and focus on Execution environment frame. This lets you define your own customized condition filter, by writing a small script which outputs, or not, the + true string on stdout when it is ran. To define the command, enter it in the + Appears if the command outputs "true" entry box. @@ -991,9 +1078,10 @@ - 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). @@ -1005,13 +1093,16 @@ binary is currently running. + Click on the Environment tab to show the page which will permit you to configure your environment-based conditions, + and focus on Execution environment frame. To define the binary, enter its name in the Appears if the binary is running + entry box, or click on Browse to select a file on the file system. @@ -1029,8 +1120,8 @@ 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). diff --git a/docs/nact/C/nact-edit.xml b/docs/nact/C/nact-edit.xml index 054384f1..0e9bfeb4 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. @@ -22,6 +22,7 @@ Multiple selection is possible in &appname;. You can extend the current selection + by pressing Ctrl or Shift while selecting an item to add to the selection. diff --git a/docs/nact/C/nact-execution.xml b/docs/nact/C/nact-execution.xml index 7dddceaa..828d31ba 100644 --- a/docs/nact/C/nact-execution.xml +++ b/docs/nact/C/nact-execution.xml @@ -8,6 +8,7 @@ As we have already seen, the command to be executed is configured + in the Command page. @@ -19,7 +20,10 @@ Available parameters - In the Command page, click on Legend + + In the Command page, + + click on Legend button to see the list of available parameters.
@@ -40,23 +44,27 @@
+ The Legend button has a toggling action: + click once to display the Parameter Legend dialog box; click a second time to hide it. - The word «sp;first&spraquo; may be misleading - as it only refers to the list of selected items internally provided by - the file manager to the &prodname; plugin. + + The word «sp;first&spraquo; may be + misleading as it only refers to the list of selected items + internally provided by the file manager to the &prodname; plugin. - In particular, it has nothing to do with the - visual selection you may - have done in the file manager window. And, in fact, which is the - «sp;first&spraquo; selected item in a - multiple selection is absolutely undefined and rather unpredictable. + In particular, it has nothing to do with + the visual selection you may have done in the file manager window. + + And, in fact, which is the «sp;first&spraquo; + selected item in a multiple selection is absolutely undefined + and rather unpredictable. @@ -67,8 +75,11 @@ Your action may be executed in a particular working directory. + You may specify it in the Command tab, in the + Working directory entry box, or by clicking + on Browse to select a folder on the filesystem. @@ -89,26 +100,29 @@
- The working directory defaults to %d, which runs - the command in the base directory of the (first) selected item. + The working directory defaults to %d, which + runs the command in the base directory of the (first) selected + item. In the particular case of the %d parameter, + the «sp;first&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. How should the action be executed ? - 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. + Click on the Execution tab to show the page which configures the execution of your command. @@ -228,8 +242,10 @@
If the execution mode of the command is Normal, + and if you know that the application will send a remove message with the DESKTOP_STARTUP_ID environment variable set, + then check the Startup notify checkbox. @@ -244,9 +260,10 @@ Window class If the execution mode of the command is Normal, - and if you know that the application will map at least one window with a - given class name, - then enter that name into the Startup Window Manager class + and if you know that the application will map at least one window + with a given class name, then enter that name into the + + Startup Window Manager class entry box. @@ -276,29 +293,30 @@
- Enter in the Execute as user entry box the username - or the UID of the user your command will be run as. + Enter in the Execute as user entry box the + username or the UID of the user your command + will be run as. - 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. Multiple executions - 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. - 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. 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. Though some parameters are not depending on the count of the @@ -323,7 +341,8 @@ 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. When the selection contains more than one item: @@ -332,16 +351,17 @@ 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; - 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; @@ -597,11 +617,12 @@ echo pierre paul jacques pierre - This is because the first relevant parameter here - is %B. The command is then run only once, replacing - %B with the space-separated list of basenames. As - the command is only run once, the %b is substituted - only once with the (first) basename. + This is because the first relevant + parameter here is %B. The command is then + run only once, replacing %B with the + space-separated list of basenames. As the command is only run + once, the %b is substituted only once with + the (first) basename. diff --git a/docs/nact/C/nact-menus.xml b/docs/nact/C/nact-menus.xml index da60c5ea..5290cade 100644 --- a/docs/nact/C/nact-menus.xml +++ b/docs/nact/C/nact-menus.xml @@ -1,19 +1,22 @@ Organizing actions in menus - 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. In order to create a new menu, choose + File + New menu . - A menu may be created anywhere in the list of your actions, but inside - of an action (i.e. not between two profiles of an action). + A menu may be created anywhere in the list of your actions, but + inside of an action (i.e. not between two profiles + of an action). As an action, the exact place where a new menu will be inserted @@ -26,10 +29,12 @@ - The new menu is inserted just before the current action or menu. + The new menu is inserted just before the current action or + menu. - 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. @@ -39,21 +44,23 @@ - The new menu is inserted at the correct place, regarding the default - «sp;New Nautilus menu&spraquo; label. + The new menu is inserted at the correct place, regarding the + + default «sp;New Nautilus menu&spraquo; + label. - 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. - 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. diff --git a/docs/nact/C/nact-misc.xml b/docs/nact/C/nact-misc.xml dissimilarity index 68% index 6eb3238c..23bd8dbd 100644 --- a/docs/nact/C/nact-misc.xml +++ b/docs/nact/C/nact-misc.xml @@ -1,8 +1,11 @@ - - 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; + diff --git a/docs/nact/C/nact-prefs.xml b/docs/nact/C/nact-prefs.xml index ff74927f..93dd06b8 100644 --- a/docs/nact/C/nact-prefs.xml +++ b/docs/nact/C/nact-prefs.xml @@ -3,7 +3,9 @@ Choose + Edit + Preferences 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 00d40563..c23c973d 100644 --- a/docs/nact/C/nact-profiles.xml +++ b/docs/nact/C/nact-profiles.xml @@ -8,7 +8,8 @@ Open a terminal here - 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. 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 + File + New profile . @@ -55,8 +58,8 @@ set on your action. - 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. If the conditions defined in a profile are met, then this profile @@ -68,13 +71,13 @@ manager 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. + 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. - 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. 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 e05e49fc..2f7f72f8 100644 --- a/docs/nact/C/nact-properties.xml +++ b/docs/nact/C/nact-properties.xml @@ -1,7 +1,7 @@ Accessing and editing item properties - An item has bot editable and read-only properties + An item has both editable and read-only properties.
diff --git a/docs/nact/C/nact-save.xml b/docs/nact/C/nact-save.xml index f9150fb7..7cf2220c 100644 --- a/docs/nact/C/nact-save.xml +++ b/docs/nact/C/nact-save.xml @@ -5,20 +5,25 @@ + Ctrl S + File + Save . 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. &prodname; also has an Auto-save feature which is configurable in + Preferences dialog box. diff --git a/docs/nact/C/nact-sorting.xml b/docs/nact/C/nact-sorting.xml index dc0e2e22..1a820b55 100644 --- a/docs/nact/C/nact-sorting.xml +++ b/docs/nact/C/nact-sorting.xml @@ -1,8 +1,10 @@ Sorting the items list - Your actions and menus will be displayed in file manager context menus - in the same order that they are listed in the Items list, + Your actions and menus will be displayed in file manager context + menus in the same order that they are listed in the + + Items list, on the left pane of the main &appname; window. @@ -11,8 +13,8 @@ - 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, @@ -26,8 +28,8 @@ Alphabetically sorting your actions and menus - 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.
Sort buttons in the main window diff --git a/docs/nact/C/nact-starting.xml b/docs/nact/C/nact-starting.xml index 362f256f..d2ba8969 100644 --- a/docs/nact/C/nact-starting.xml +++ b/docs/nact/C/nact-starting.xml @@ -27,6 +27,7 @@ nautilus-actions-config-tool + then press Return. @@ -40,6 +41,7 @@ + then press Return. @@ -64,8 +66,8 @@ 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. @@ -229,8 +231,8 @@ Toolbar. - 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 View Toolbars @@ -243,12 +245,13 @@ 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;. - 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. Invalid items are displayed in red color. @@ -270,8 +273,9 @@ Properties tabs. - 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. @@ -280,8 +284,8 @@ - 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. @@ -312,8 +316,9 @@ - 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. @@ -323,8 +328,9 @@ - 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. @@ -334,8 +340,9 @@ - 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. @@ -345,8 +352,9 @@ - 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. @@ -356,8 +364,9 @@ - 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. @@ -367,8 +376,9 @@ - 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. @@ -393,10 +403,12 @@ currently selected row in the items list. - 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. + The «sp;read-only&spraquo; icon is displayed in @@ -410,8 +422,8 @@ Creating your first action - 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. Checking for prerequisites @@ -425,8 +437,8 @@ 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: @@ -479,10 +491,13 @@
- In the Items list, the new action is displayed in italic characters. + + In the Items list, the new action is + displayed in italic characters. - 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. As another reminder that there is some pending modifications, @@ -492,35 +507,41 @@ Qualifying your new action - 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. + Enter My first action + in the Context label entry box. - The Context label entry box contains the label - of the action as you want it to be displayed in the file manager - context menu. + + The Context label entry box contains + the label of the action as you want it to be displayed in + the file manager context menu. - 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 Items list - 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 + + Items list and will never be candidate + to be displayed in the file manager context menus. Enter This will execute an action with some parameters + in the Tooltip entry box. + The Tooltip entry box contains the text you want to be displayed as a short help to your action. @@ -528,20 +549,25 @@ Select + in the Icon drop-down list. - The Icon selection defines the icon which will - be associated with your action in file manager context menus and in - the toolbar. + + The Icon selection defines the icon + which will be associated with your action in file manager + context menus and in the toolbar. - You have two ways of choosing the icon associated to your action: + You have two ways of choosing the icon associated to your + action: - Click on the Icon drop-down list to select an icon. + + Click on the Icon drop-down list + to select an icon. @@ -562,6 +588,7 @@ + Click on the Command tab to show the page which will permit you to enter the command. @@ -589,13 +616,15 @@ - Enter zenity in the Path - entry box. + Enter zenity in the + + Path entry box. - The Path entry box defines the command which - will be executed when you will select your action in the file manager - context menu. + + The Path entry box defines the command + which will be executed when you will select your action in + the file manager context menu. You have two ways of defining the command to be executed: @@ -603,6 +632,7 @@ + Enter it in the Path entry box. @@ -621,21 +651,27 @@ + Enter --info --text='%c selected item(s): %U' + in the Parameters entry box. - The Parameters 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. + + The Parameters 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. + If both Path and Parameters - are empty, then this action will be considered as invalid: it will be - displayed in red in Items list 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: + + it will be displayed in red in Items list + and will never be candidate to be displayed in the file + manager context menus. diff --git a/docs/nact/C/nact-where.xml b/docs/nact/C/nact-where.xml index 2847311c..4b94df90 100644 --- a/docs/nact/C/nact-where.xml +++ b/docs/nact/C/nact-where.xml @@ -22,6 +22,7 @@ selected (or not). + Click on the Action tab to show the page which will permit you to configure the locations your action targets. @@ -103,17 +104,20 @@ + the Context label as a label, + the Icon, these two properties being associated with the + Tooltip. @@ -127,9 +131,9 @@ - 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). @@ -142,17 +146,20 @@ + the Toolbar label as a label, + the Icon, these two properties being associated with the + Tooltip. @@ -170,14 +177,16 @@ those used in menus. By unchecking the Use same label for icon in the toolbar 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. - 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). @@ -193,8 +202,8 @@ Defining no target at all If no target is defined, - i.e. if the three checkboxes are unchecked, then your action - will never be displayed. + i.e. if the three checkboxes are unchecked, + then your action will never be displayed. -- 2.11.4.GIT