eg_translations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
eg_translations [2017/03/19 14:20] – [Adding the custom string to PO file] cernin | eg_translations [2022/01/14 12:39] – [Making the custom string in TPAC translatable.] tmccanna | ||
---|---|---|---|
Line 16: | Line 16: | ||
//PO// files are the files containing the translations. Each language have its own PO file, e.g., Czech translation | //PO// files are the files containing the translations. Each language have its own PO file, e.g., Czech translation | ||
- | Usually an application is used to manage translations in PO files, e.g., desktop tool [[ https:// | + | Usually an application is used to manage translations in PO files, e.g., desktop tool [[ https:// |
The PO file consists of pairs of the text extracted from the code: | The PO file consists of pairs of the text extracted from the code: | ||
Line 57: | Line 57: | ||
==== Support for individual languages in Evergreen release ==== | ==== Support for individual languages in Evergreen release ==== | ||
- | Currently there are over 30 Evergreeen | + | Currently there are over 30 Evergreen |
* At least 70 % of translation is complete | * At least 70 % of translation is complete | ||
Line 65: | Line 65: | ||
* The en-* variant of translations have an exception from criteria above as they are a special case (there is no need to translate all strings). | * The en-* variant of translations have an exception from criteria above as they are a special case (there is no need to translate all strings). | ||
- | NOTE: These criteria are not a " | + | NOTE: These criteria are not a " |
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 99: | Line 99: | ||
If you have any questions, please, contact Evergreen translations coordinator [[ mailto: | If you have any questions, please, contact Evergreen translations coordinator [[ mailto: | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
Line 118: | Line 109: | ||
- Select required language (e.g. Czech or Spanish ….) | - Select required language (e.g. Czech or Spanish ….) | ||
- Open the // | - Open the // | ||
- | - Select //PO format// and submit the //Request for download// button ((You can also request for download of [[https:// | + | - Select //PO format// and submit the //Request for download// button ((You can also request for download of [[https:// |
- Download the file and rename it according to the desired language (e.g., cs-CZ.po for Czech or es-ES.po for Spanish) | - Download the file and rename it according to the desired language (e.g., cs-CZ.po for Czech or es-ES.po for Spanish) | ||
- Copy the downloaded file to / | - Copy the downloaded file to / | ||
Line 133: | Line 124: | ||
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, | 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 147: | Line 135: | ||
see the documentation: | see the documentation: | ||
* [[http:// | * [[http:// | ||
- | * [[http:// | + | * [[http:// |
+ | |||
+ | ===== Adding Translations Through Angular Interfaces ===== | ||
+ | |||
+ | The newer Angular administration interfaces provide a button to add translations (for example, the MARC Coded Value Map controls the Audience dropdown fields in the OPAC advanced search), but you will need to edit a file in order to enable it for each language. | ||
+ | |||
+ | - Edit Open-ILS/ | ||
+ | - Modify the locales array (eg, locales: [' | ||
+ | - Recompile Angular: ng build --prod | ||
+ | |||
==== Adding the custom string to PO file ==== | ==== Adding the custom string to PO file ==== |
eg_translations.txt · Last modified: 2023/10/31 16:28 by bmagic