Commit 6c74c448 authored by Pierre Wieser's avatar Pierre Wieser

Fix various typos and grammar issues

Fix #727525 reported by Anders Jonsson
parent 5cc2b86a
......@@ -82,7 +82,7 @@ Possible values are:
- "GConfSchemaV1": this used to be the historical export format. The exported file may later be imported via Import assistant of the Nautilus-Actions Configuration Tool, or via the gconftool-2 --import-schema-file command-line tool.
- "GConfSchemaV2": a lighter while still compatible schema. The exported file may later be imported via Import assistant of the Nautilus-Actions Configuration Tool, or via the gconftool-2 --import-schema-file command-line tool.
- "GConfEntry": this should be the preferred format for newly exported actions. The exported file may later be imported via Import assistant of the Nautilus-Actions Configuration Tool, or via the gconftool-2 --load command-line tool.
- "Ask": the user will be asked at runtime for the format he wishes use.</long>
- "Ask": the user will be asked at runtime for the format he wishes to use.</long>
</locale>
<default>/tmp</default>
</schema>
......@@ -163,7 +163,7 @@ Possible values are:
<type>string</type>
<locale name="C">
<short>Last import mode chosen by the user</short>
<long>Last import mode chosen by the user when he is asked for in import mode. Possible values are:
<long>Last import mode chosen by the user when he was asked for an import mode. Possible values are:
- "NoImport": do not import an action whose UUID already exists,
- "Renumber": allocate a new UUID if the imported UUID already exists,
- "Override": override the existing action with the imported one.</long>
......@@ -400,7 +400,7 @@ Possible values are:
<locale name="C">
<short>List of default schemes</short>
<long>The list of schemes proposed by default on each new profile.
A default default list is harcoded in nautilus-actions-config-tool, which may be updated by the user.</long>
A default default list is hardcoded in nautilus-actions-config-tool, which may be updated by the user.</long>
</locale>
<default>[]</default>
</schema>
......
......@@ -62,7 +62,7 @@ This specification relies on the common syntax as defined in <a href="http://sta
Please note that, in all tables below, <?php code( "Req=YES" ); ?> just means that the value is required to define a valid action (resp. menu, resp. profile). A management UI is free to handle invalid actions (resp. menus, resp. profiles), and in fact that might even be needed in order to be able to fix invalid items, and make them valid...
</p>
<h4>Desktop file identifiant</h4>
<h4>Desktop file identifier</h4>
<p>
In the rest of this specification, when a desktop file needs to be identified, we are using the basename of the file, without the extension, calling this a <i>desktop_file_id</i>.
......@@ -298,7 +298,7 @@ Another choice might also be:
Profile is identified by its <i>profile_id</i>, as an ASCII string.
</p>
<p>
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifiant, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifier, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
</p>
<p>
When several profiles are defined for an action, only the first valid profile whose conditions are met at runtime is selected to be made available in the context menu.
......
......@@ -64,7 +64,7 @@ This specification relies on the common syntax defined in <?php DES(); ?>. We ar
Please note that, in all tables below, <?php code( "Req=YES" ); ?> just means that the value is required to define a valid action (resp. menu, resp. profile). A management UI is free to handle invalid actions (resp. menus, resp. profiles), and in fact that might even be needed in order to be able to fix invalid items, and make them valid...
</p>
<h4>Desktop file identifiant</h4>
<h4>Desktop file identifier</h4>
<p>
In the rest of this specification, when a desktop file needs to be identified, we are using the basename of the file, without the extension, calling this a <i>desktop_file_id</i>.
......@@ -303,7 +303,7 @@ Another choice might also be:
Profile is identified by its <i>profile_id</i>, as an ASCII string.
</p>
<p>
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifiant, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifier, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
</p>
<p>
When several profiles are defined for an action, only the first valid profile whose conditions are met at runtime is selected to be made available in the context menu.
......
......@@ -64,7 +64,7 @@ This specification relies on the common syntax defined in <?php DES(); ?>. We ar
Please note that, in all tables below, <?php code( "Req=YES" ); ?> just means that the value is required to define a valid action (resp. menu, resp. profile). A management UI is free to handle invalid actions (resp. menus, resp. profiles), and in fact that might even be needed in order to be able to fix invalid items, and make them valid...
</p>
<h4>Desktop file identifiant</h4>
<h4>Desktop file identifier</h4>
<p>
In the rest of this specification, when a desktop file needs to be identified, we are using the basename of the file, without the extension, calling this a <i>desktop_file_id</i>.
......@@ -303,7 +303,7 @@ Another choice might also be:
Profile is identified by its <i>profile_id</i>, as an ASCII string.
</p>
<p>
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifiant, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifier, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
</p>
<p>
When several profiles are defined for an action, only the first valid profile whose conditions are met at runtime is selected to be made available in the context menu.
......
......@@ -64,7 +64,7 @@ This specification relies on the common syntax defined in <?php DES(); ?>. We ar
Please note that, in all tables below, <?php code( "Req=YES" ); ?> just means that the value is required to define a valid action (resp. menu, resp. profile). A management UI is free to handle invalid actions (resp. menus, resp. profiles), and in fact that might even be needed in order to be able to fix invalid items, and make them valid...
</p>
<h4>Desktop file identifiant</h4>
<h4>Desktop file identifier</h4>
<p>
In the rest of this specification, when a desktop file needs to be identified, we are using the basename of the file, without the extension, calling this a <i>desktop_file_id</i>.
......@@ -303,7 +303,7 @@ Another choice might also be:
Profile is identified by its <i>profile_id</i>, as an ASCII string.
</p>
<p>
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifiant, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
Each profile defined in the "<?php code( "Profiles" ); ?>" key, whether statically by its <i>profile_id</i> identifier, or as the result of an evaluated command, must be defined in a <?php code( "[X-Action-Profile <i>profile_id</i>]" ); ?> group.
</p>
<p>
When several profiles are defined for an action, only the first valid profile whose conditions are met at runtime is selected to be made available in the context menu.
......
......@@ -131,7 +131,7 @@
<para>
<ulink url="ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng">libUUID</ulink>
is the universally unique ID library used to automatically generate a
unique identifiant at item creation.
unique identifier at item creation.
</para>
</listitem>
<listitem>
......@@ -223,7 +223,7 @@
</para>
<para>
This defaults to &quot;na-desktop&quot; which is the internal
identifiant of the I/O provider which manages
identifier of the I/O provider which manages
<filename>.desktop</filename> files.
</para>
</formalpara>
......
......@@ -398,13 +398,13 @@ initialize_window( NAImporterAsk *editor, GtkWindow *toplevel )
if( NA_IS_OBJECT_ACTION( editor->private->importing )){
/* i18n: The action <action_label> imported from <file> has the same id than <existing_label> */
label = g_strdup_printf(
_( "The action \"%s\" imported from \"%s\" has the same identifiant than the already existing \"%s\"." ),
_( "The action \"%s\" imported from \"%s\" has the same identifier than the already existing \"%s\"." ),
imported_label, editor->private->parms->uri, existing_label );
} else {
/* i18n: The menu <menu_label> imported from <file> has the same id than <existing_label> */
label = g_strdup_printf(
_( "The menu \"%s\" imported from \"%s\" has the same identifiant than the already existing \"%s\"." ),
_( "The menu \"%s\" imported from \"%s\" has the same identifier than the already existing \"%s\"." ),
imported_label, editor->private->parms->uri, existing_label );
}
......
......@@ -361,7 +361,7 @@ This command should include a 'COMMAND' keyword, which will be substituted at ru
<child type="tab">
<object class="GtkLabel" id="label700">
<property name="visible">True</property>
<property name="tooltip_text" translatable="yes">This tab lets you specify parameters needed for. some execution modes.</property>
<property name="tooltip_text" translatable="yes">This tab lets you specify parameters needed for some execution modes.</property>
<property name="label" translatable="yes">Runtime E_xecution</property>
<property name="use_underline">True</property>
</object>
......
......@@ -977,7 +977,7 @@ add_about_item( NautilusActions *plugin, GList *menu )
about_item = nautilus_menu_item_new(
"AboutNautilusActions",
_( "About Nautilus-Actions" ),
_( "Display some informations about Nautilus-Actions" ),
_( "Display some information about Nautilus-Actions" ),
na_about_get_icon_name());
g_signal_connect_data(
......
......@@ -57,7 +57,7 @@ static const gchar *program_summary = N_( "Print a menu or an action to stdout."
static GOptionEntry entries[] = {
{ "id" , 'i', 0, G_OPTION_ARG_STRING , &id,
N_( "The identifiant of the menu or the action to be printed" ), N_( "<STRING>" ) },
N_( "The identifier of the menu or the action to be printed" ), N_( "<STRING>" ) },
{ "format" , 'f', 0, G_OPTION_ARG_STRING, &format,
/* i18n: 'Desktop1' here is the internal identifier of an export format; it is not translatable */
N_( "An export format [Desktop1]" ), N_( "<STRING>" ) },
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment