Differences

This shows you the differences between two versions of the page.

--- eg_translations [2017/03/19 14:14] – cernin
+++ eg_translations [2017/03/19 14:20] – [Adding the custom string to PO file] cernin
@@ Line 125: / Line 125: @@
 Analogically, to update the web staff client translations, download the translation template //webstaff// and copy it to ///openils/var/template/data/locale/staff//.
-NOTE: It is necessary to set specific  language previously, see the documentation: [[http://docs.evergreen-ils.org/2.10/_setting_a_default_language_and_adding_optional_languages.html | Setting a default language and adding optional languages]].
+NOTE: It is necessary to set specific  language previously - see the documentation: [[http://docs.evergreen-ils.org/2.10/_setting_a_default_language_and_adding_optional_languages.html | Setting a default language and adding optional languages]].
 ===== Making the custom string in TPAC translatable. =====
@@ Line 132: / Line 132: @@
-As Evergreen supports multiple languages, it is important, that any customization to Evergreen’s default text (e.g., links in top or bottom navigation in OPAC, or any other kind of custom information on catalog homepage etc.) uses the localization function. To make the custom string translatable, the string must be in English and must be surrounded by   **[% l('**   ** ') %]**  (( The [% ... %] signifies a TT block, which can contain one or more TT processing instructions. l(" ... "); is a function that marks text for localization (translation). ))
+As Evergreen supports multiple languages, it is important, that any customization to Evergreen’s default text  uses the localization function. To make the custom string translatable, the string must be in English and must be surrounded by   **[% l('**   ** ') %]**  (( The [% ... %] signifies a TT block, which can contain one or more TT processing instructions. l(" ... "); is a function that marks text for localization (translation). ))
@@ Line 151: / Line 151: @@
 ==== Adding the custom string to PO file ====
-After you have added custom text in translatable form to a TT2 template, you need to add the custom strings and its translations to the PO file containing the translations (the PO files are stored  in  ///openils/var/template/data/locale/ // )
+After you have added custom texts in translatable form to a TT2 template, you need to add the custom strings and its translations to the PO file containing the translations (the PO files are stored  in  ///openils/var/template/data/locale/ // )
 Note: It is good practice to save backup copy of the original PO file before changing it.