Commit 1e7f6d1e authored by jhodgdon's avatar jhodgdon

Issue #2855660 by jhodgdon, eojthebrave: Expand chapter 10.5 Translating Configuration

parent 34e2dc1f
......@@ -37,9 +37,9 @@ _Default time zone_.
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ >
_Site information_ (_admin/config/system/site-information_) to change the _Site
name_, _Slogan_, administrative _Email address_, or the _Default front page_
path.
_Basic site settings_ (_admin/config/system/site-information_) to change the
_Site name_, _Slogan_, administrative _Email address_, or the _Default front
page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -29,6 +29,28 @@ must have at least two languages. See <<language-add>>.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or
edited in the site's primary language. For example, to translate the site name,
you need to find the page where you would edit the site name (see
<<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something
similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and
click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this
manner. Views configuration is an exception, because the translation editing
form is nothing like the view editing form, and it is complex and hierarchical
rather than being a simple form with just a few fields. As an example of how to
translate a view, here are the steps to translate the labels in the Recipes view
to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_
(_admin/structure/views_).
......@@ -52,7 +74,7 @@ image:images/language-config-translate-recipes-view.png["Translate the Recipes v
. Find _Displays_ > _Master display settings_ > _Recipes default display
options_ > _Filters_ > _(Empty) taxonomy term ID_ > _Find recipes
using... Expose_. In the _Label_ field, enter "Encontrar rectas usando...".
using... Expose_. In the _Label_ field, enter "Encontrar recetas usando...".
. Click _Save translation_.
......@@ -66,15 +88,33 @@ display settings section of the Recipes view.
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation
pages:
** To translate the site name, navigate in the _Manage_ administrative menu to
_Configuration_ > _System_ > _Site information_ > _Translate system
_Configuration_ > _System_ > _Basic site settings_ > _Translate system
information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu
to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_
from the dropdown button in the _Website feedback_ row.
in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu
to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the
dropdown button for the menu whose name you want to translate.
** Menu items within a menu are considered to be content (not configuration);
see <<language-content-config>> to enable translation. Once translation is
enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_
(_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu
whose links you want to translate. Click _Translate_ in the dropdown button for
the link you want to translate.
** To translate field labels on a content type, navigate in the _Manage_
administrative menu to _Structure_ > _Content types_
(_admin/structure/types_). Click _Manage fields_ in the dropdown button for the
content type whose field labels you want to edit. Click _Translate_ in the
dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
......@@ -37,9 +37,9 @@ _Default time zone_.
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ >
_Site information_ (_admin/config/system/site-information_) to change the _Site
name_, _Slogan_, administrative _Email address_, or the _Default front page_
path.
_Basic site settings_ (_admin/config/system/site-information_) to change the
_Site name_, _Slogan_, administrative _Email address_, or the _Default front
page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -29,6 +29,28 @@ must have at least two languages. See <<language-add>>.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or
edited in the site's primary language. For example, to translate the site name,
you need to find the page where you would edit the site name (see
<<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something
similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and
click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this
manner. Views configuration is an exception, because the translation editing
form is nothing like the view editing form, and it is complex and hierarchical
rather than being a simple form with just a few fields. As an example of how to
translate a view, here are the steps to translate the labels in the Recipes view
to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_
(_admin/structure/views_).
......@@ -66,15 +88,33 @@ display settings section of the Recipes view.
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation
pages:
** To translate the site name, navigate in the _Manage_ administrative menu to
_Configuration_ > _System_ > _Site information_ > _Translate system
_Configuration_ > _System_ > _Basic site settings_ > _Translate system
information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu
to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_
from the dropdown button in the _Website feedback_ row.
in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu
to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the
dropdown button for the menu whose name you want to translate.
** Menu items within a menu are considered to be content (not configuration);
see <<language-content-config>> to enable translation. Once translation is
enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_
(_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu
whose links you want to translate. Click _Translate_ in the dropdown button for
the link you want to translate.
** To translate field labels on a content type, navigate in the _Manage_
administrative menu to _Structure_ > _Content types_
(_admin/structure/types_). Click _Manage fields_ in the dropdown button for the
content type whose field labels you want to edit. Click _Translate_ in the
dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
......@@ -37,9 +37,9 @@ _Default time zone_.
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ >
_Site information_ (_admin/config/system/site-information_) to change the _Site
name_, _Slogan_, administrative _Email address_, or the _Default front page_
path.
_Basic site settings_ (_admin/config/system/site-information_) to change the
_Site name_, _Slogan_, administrative _Email address_, or the _Default front
page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -29,6 +29,28 @@ must have at least two languages. See <<language-add>>.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or
edited in the site's primary language. For example, to translate the site name,
you need to find the page where you would edit the site name (see
<<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something
similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and
click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this
manner. Views configuration is an exception, because the translation editing
form is nothing like the view editing form, and it is complex and hierarchical
rather than being a simple form with just a few fields. As an example of how to
translate a view, here are the steps to translate the labels in the Recipes view
to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_
(_admin/structure/views_).
......@@ -66,15 +88,33 @@ display settings section of the Recipes view.
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation
pages:
** To translate the site name, navigate in the _Manage_ administrative menu to
_Configuration_ > _System_ > _Site information_ > _Translate system
_Configuration_ > _System_ > _Basic site settings_ > _Translate system
information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu
to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_
from the dropdown button in the _Website feedback_ row.
in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu
to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the
dropdown button for the menu whose name you want to translate.
** Menu items within a menu are considered to be content (not configuration);
see <<language-content-config>> to enable translation. Once translation is
enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_
(_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu
whose links you want to translate. Click _Translate_ in the dropdown button for
the link you want to translate.
** To translate field labels on a content type, navigate in the _Manage_
administrative menu to _Structure_ > _Content types_
(_admin/structure/types_). Click _Manage fields_ in the dropdown button for the
content type whose field labels you want to edit. Click _Translate_ in the
dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
......@@ -37,9 +37,9 @@ _Default time zone_.
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ >
_Site information_ (_admin/config/system/site-information_) to change the _Site
name_, _Slogan_, administrative _Email address_, or the _Default front page_
path.
_Basic site settings_ (_admin/config/system/site-information_) to change the
_Site name_, _Slogan_, administrative _Email address_, or the _Default front
page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -29,6 +29,28 @@ must have at least two languages. See <<language-add>>.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or
edited in the site's primary language. For example, to translate the site name,
you need to find the page where you would edit the site name (see
<<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something
similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and
click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this
manner. Views configuration is an exception, because the translation editing
form is nothing like the view editing form, and it is complex and hierarchical
rather than being a simple form with just a few fields. As an example of how to
translate a view, here are the steps to translate the labels in the Recipes view
to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_
(_admin/structure/views_).
......@@ -66,15 +88,33 @@ display settings section of the Recipes view.
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation
pages:
** To translate the site name, navigate in the _Manage_ administrative menu to
_Configuration_ > _System_ > _Site information_ > _Translate system
_Configuration_ > _System_ > _Basic site settings_ > _Translate system
information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu
to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_
from the dropdown button in the _Website feedback_ row.
in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu
to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the
dropdown button for the menu whose name you want to translate.
** Menu items within a menu are considered to be content (not configuration);
see <<language-content-config>> to enable translation. Once translation is
enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_
(_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu
whose links you want to translate. Click _Translate_ in the dropdown button for
the link you want to translate.
** To translate field labels on a content type, navigate in the _Manage_
administrative menu to _Structure_ > _Content types_
(_admin/structure/types_). Click _Manage fields_ in the dropdown button for the
content type whose field labels you want to edit. Click _Translate_ in the
dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
......@@ -35,7 +35,7 @@ Change basic site information such as _Site name_, _Slogan_, _Default time zone_
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ > _Site information_ (_admin/config/system/site-information_) to change the _Site name_, _Slogan_, administrative _Email address_, or the _Default front page_ path.
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ > _Basic site settings_ (_admin/config/system/site-information_) to change the _Site name_, _Slogan_, administrative _Email address_, or the _Default front page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -28,6 +28,18 @@ Translate the labels on the Recipes view page into Spanish.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or edited in the site's primary language. For example, to translate the site name, you need to find the page where you would edit the site name (see <<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this manner. Views configuration is an exception, because the translation editing form is nothing like the view editing form, and it is complex and hierarchical rather than being a simple form with just a few fields. As an example of how to translate a view, here are the steps to translate the labels in the Recipes view to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ (_admin/structure/views_).
. Locate the Recipes view and click _Translate_ from the dropdown button.
......@@ -55,11 +67,17 @@ image:images/language-config-translate-recipes-view.png["Translate the Recipes v
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation pages:
** To translate the site name, navigate in the _Manage_ administrative menu to _Configuration_ > _System_ > _Basic site settings_ > _Translate system information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_ in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the dropdown button for the menu whose name you want to translate.
** To translate the site name, navigate in the _Manage_ administrative menu to _Configuration_ > _System_ > _Site information_ > _Translate system information_ (_admin/config/system/site-information/translate_).
** Menu items within a menu are considered to be content (not configuration); see <<language-content-config>> to enable translation. Once translation is enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu whose links you want to translate. Click _Translate_ in the dropdown button for the link you want to translate.
** To translate the contact form, navigate in the _Manage_ administrative menu to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_ from the dropdown button in the _Website feedback_ row.
** To translate field labels on a content type, navigate in the _Manage_ administrative menu to _Structure_ > _Content types_ (_admin/structure/types_). Click _Manage fields_ in the dropdown button for the content type whose field labels you want to edit. Click _Translate_ in the dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
......@@ -37,9 +37,9 @@ _Default time zone_.
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ >
_Site information_ (_admin/config/system/site-information_) to change the _Site
name_, _Slogan_, administrative _Email address_, or the _Default front page_
path.
_Basic site settings_ (_admin/config/system/site-information_) to change the
_Site name_, _Slogan_, administrative _Email address_, or the _Default front
page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -29,6 +29,28 @@ must have at least two languages. See <<language-add>>.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or
edited in the site's primary language. For example, to translate the site name,
you need to find the page where you would edit the site name (see
<<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something
similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and
click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this
manner. Views configuration is an exception, because the translation editing
form is nothing like the view editing form, and it is complex and hierarchical
rather than being a simple form with just a few fields. As an example of how to
translate a view, here are the steps to translate the labels in the Recipes view
to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_
(_admin/structure/views_).
......@@ -66,15 +88,33 @@ display settings section of the Recipes view.
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation
pages:
** To translate the site name, navigate in the _Manage_ administrative menu to
_Configuration_ > _System_ > _Site information_ > _Translate system
_Configuration_ > _System_ > _Basic site settings_ > _Translate system
information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu
to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_
from the dropdown button in the _Website feedback_ row.
in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu
to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the
dropdown button for the menu whose name you want to translate.
** Menu items within a menu are considered to be content (not configuration);
see <<language-content-config>> to enable translation. Once translation is
enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_
(_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu
whose links you want to translate. Click _Translate_ in the dropdown button for
the link you want to translate.
** To translate field labels on a content type, navigate in the _Manage_
administrative menu to _Structure_ > _Content types_
(_admin/structure/types_). Click _Manage fields_ in the dropdown button for the
content type whose field labels you want to edit. Click _Translate_ in the
dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
......@@ -37,9 +37,9 @@ _Default time zone_.
===== Configuring the basic site information
. In the _Manage_ administrative menu, navigate to _Configuration_ > _System_ >
_Site information_ (_admin/config/system/site-information_) to change the _Site
name_, _Slogan_, administrative _Email address_, or the _Default front page_
path.
_Basic site settings_ (_admin/config/system/site-information_) to change the
_Site name_, _Slogan_, administrative _Email address_, or the _Default front
page_ path.
. Fill in the available fields as appropriate for your site.
+
......
......@@ -29,6 +29,28 @@ must have at least two languages. See <<language-add>>.
==== Steps
The basic steps for translating any configuration on your site are:
. Locate the page where the configuration you want to translate is created or
edited in the site's primary language. For example, to translate the site name,
you need to find the page where you would edit the site name (see
<<config-basic>>).
. Find a link, tab, or button on the page that says "Translate" or something
similar. Click this link, tab, or button.
. Find a button that will let you add a translation in the desired language, and
click this button.
. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this
manner. Views configuration is an exception, because the translation editing
form is nothing like the view editing form, and it is complex and hierarchical
rather than being a simple form with just a few fields. As an example of how to
translate a view, here are the steps to translate the labels in the Recipes view
to Spanish:
. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_
(_admin/structure/views_).
......@@ -66,15 +88,33 @@ display settings section of the Recipes view.
* Translate the page title in the Vendors view.
* Translate other configuration, such as the site name and the contact form:
* Translate other configuration. Some examples of where to find the translation
pages:
** To translate the site name, navigate in the _Manage_ administrative menu to
_Configuration_ > _System_ > _Site information_ > _Translate system
_Configuration_ > _System_ > _Basic site settings_ > _Translate system
information_ (_admin/config/system/site-information/translate_).
** To translate the contact form, navigate in the _Manage_ administrative menu
to _Structure_ > _Contact forms_ (_admin/structure/contact_). Click _Translate_
from the dropdown button in the _Website feedback_ row.
in the dropdown button in the _Website feedback_ row.
** To translate the name of a menu, navigate in the _Manage_ administrative menu
to _Structure_ > _Menus_ (_admin/structure/menu_). Click _Translate_ in the
dropdown button for the menu whose name you want to translate.
** Menu items within a menu are considered to be content (not configuration);
see <<language-content-config>> to enable translation. Once translation is
enabled, navigate in the _Manage_ administrative menu to _Structure_ > _Menus_
(_admin/structure/menu_). Click _Edit menu_ in the dropdown button for the menu
whose links you want to translate. Click _Translate_ in the dropdown button for
the link you want to translate.
** To translate field labels on a content type, navigate in the _Manage_
administrative menu to _Structure_ > _Content types_
(_admin/structure/types_). Click _Manage fields_ in the dropdown button for the
content type whose field labels you want to edit. Click _Translate_ in the
dropdown button for the field whose label you want to edit.
* Translate content. See <<language-content-translate>>.
......
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