eg_translations
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
eg_translations [2017/02/28 07:34] – created cernin | eg_translations [2017/03/19 14:20] – [Adding the custom string to PO file] cernin | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Evergreen translations ====== | ====== Evergreen translations ====== | ||
- | Evergreen translations can be found and managed in [[https:// | + | Evergreen translations can be found and managed in [[https:// |
===== Understanding the translations workflow ===== | ===== Understanding the translations workflow ===== | ||
Line 46: | Line 46: | ||
- When new release is being prepared, the //POT// files are generated and imported into Evergreen translation project in Launchpad. The import to Launchpad happens usually at the time when Evergreen | - When new release is being prepared, the //POT// files are generated and imported into Evergreen translation project in Launchpad. The import to Launchpad happens usually at the time when Evergreen | ||
- | - The strings in Launchpad are translated to various languages. | + | - The strings in Launchpad are translated to various languages. Also strings newly added to Evergreen can be added to Launchpad in the meantime, between beta release and X.Y.0 release. |
- Before X.Y.0 release the new //PO// files are generated from the Launchpad translation data and are included into the release. | - Before X.Y.0 release the new //PO// files are generated from the Launchpad translation data and are included into the release. | ||
Line 77: | Line 77: | ||
- Notes to translators (denoted by blue icons with " | - Notes to translators (denoted by blue icons with " | ||
- String location (under the //New translation// | - String location (under the //New translation// | ||
- | - ** Be consistent in used expressions** \\ Translate the same word or string always in the same way. It is good to make some " | + | - ** Be consistent in used expressions** \\ Translate the same word or string always in the same way. It is good to make some " |
- **Recognize the background of translated expression.** \\ Translation strings contain e.g.: | - **Recognize the background of translated expression.** \\ Translation strings contain e.g.: | ||
- standardized terms used for MARC record description in Evergreen (it is good to have national MARC fields and terms translations at hand), | - standardized terms used for MARC record description in Evergreen (it is good to have national MARC fields and terms translations at hand), | ||
Line 87: | Line 87: | ||
- **In some cases, some parts of strings should not be translated. It concerns particularly: | - **In some cases, some parts of strings should not be translated. It concerns particularly: | ||
| | ||
- | - Formatting/ | + | - Formatting(HTML)/XML tags |
- Program parameters etc. | - Program parameters etc. | ||
- ** After you have translated a string, read it again.** \\ It is good practice to review the translation and see possible mistyping or errors, missing punctuation etc. | - ** After you have translated a string, read it again.** \\ It is good practice to review the translation and see possible mistyping or errors, missing punctuation etc. | ||
Line 115: | Line 115: | ||
**Recommended practice:** | **Recommended practice:** | ||
- | - Visit the Evergreen translation site in Launchpad (https:// | + | - Visit the Evergreen translation site in Launchpad (https:// |
- Select required language (e.g. Czech or Spanish ….) | - Select required language (e.g. Czech or Spanish ….) | ||
- Open the // | - Open the // | ||
Line 125: | Line 125: | ||
Analogically, | Analogically, | ||
- | NOTE: It is necessary to set specific | + | NOTE: It is necessary to set specific |
===== Making the custom string in TPAC translatable. ===== | ===== 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, | + | 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, |
Line 151: | Line 151: | ||
==== Adding the custom string to PO file ==== | ==== Adding the custom string to PO file ==== | ||
- | After you have added custom | + | After you have added custom |
Note: It is good practice to save backup copy of the original PO file before changing it. | Note: It is good practice to save backup copy of the original PO file before changing it. | ||
Line 160: | Line 160: | ||
* It is recommended to add a note in which template and on which line the particular | * It is recommended to add a note in which template and on which line the particular | ||
- | **Example: | + | **Example: |
Line 177: | Line 177: | ||
</ | </ | ||
+ | |||
+ | **Example of living Evergreen catalog using translatable custom strings:** | ||
+ | |||
+ | http:// | ||
--------------------- | --------------------- | ||
+ | ===== Additional information ===== | ||
+ | |||
Information on Evergreen | Information on Evergreen | ||
[[evergreen-admin: | [[evergreen-admin: |
eg_translations.txt · Last modified: 2023/10/31 16:28 by bmagic