Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:architecture:localization:lokalise
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
development:architecture:localization:lokalise [2023/09/21 13:47] – [Importing Translations from VuFind®] demiankatz | development:architecture:localization:lokalise [2024/01/11 19:06] (current) – [Importing Translations from VuFind®] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Lokalise ====== | ====== Lokalise ====== | ||
- | The VuFind® project uses Lokalise to manage its internationalization. This page provides some notes on how to utilize the platform effectively. | + | The VuFind® project uses [[https:// |
===== Notes for Translators ===== | ===== Notes for Translators ===== | ||
Line 7: | Line 7: | ||
Volunteer translators can be granted access to one or more languages used by the project. It is then possible to edit and add translations through a web-based interface. If you would like to volunteer as a translator, please contact info@vufind.org and let us know which language(s) you can help with. | Volunteer translators can be granted access to one or more languages used by the project. It is then possible to edit and add translations through a web-based interface. If you would like to volunteer as a translator, please contact info@vufind.org and let us know which language(s) you can help with. | ||
- | ==== Providing Translations ==== | ||
- | // Details coming soon... // | + | ====Useful Resources==== |
+ | * Training video on YouTube: [[https://youtu.be/ | ||
+ | |||
+ | * FOLIO' | ||
+ | |||
+ | ====Getting started==== | ||
+ | 1. Log into Lokalise using the "Open project" | ||
+ | |||
+ | 2. From the dashboard, click the name of the language you are going to work on. This will bring you to the Editor view. | ||
+ | |||
+ | 3. Make sure the FILTER is set to **Untranslated** to see the list of words and phrases that need translation. **Disregard any entries labeled @parent_ini; | ||
+ | |||
+ | 4. Identify an item you'd like to translate. The term to be translated will be on the left side, and the word Empty will be on the right side. This is the view within the full list: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | 5. To enter your translation, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | 6. Lokalise will also offer options for machine-generated translations in the right hand sidebar; you can click one of those, and it will populate the text entry box with that translation. You can use that translation as it is, or you can edit it. | ||
+ | |||
+ | 7. Click **Save** when you are ready to save the translation. | ||
+ | |||
+ | |||
+ | ====Additional Suggestions==== | ||
+ | |||
+ | ===Access words in text domains=== | ||
+ | |||
+ | To access text domains within the VuFind word/phrase list, click **Filter**, **Filename**. This will allow you to focus on such areas as CallNumberFirst, | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | ===Check entire word list for formatting issues=== | ||
+ | |||
+ | To check for formatting issues within the existing language entries, click **Filter**, **QA** (Quality Assurance). You can focus on issues such as extra whitespaces, | ||
+ | |||
+ | {{: | ||
===== Notes for Administrators ===== | ===== Notes for Administrators ===== | ||
Line 17: | Line 57: | ||
==== Importing Translations from VuFind® ==== | ==== Importing Translations from VuFind® ==== | ||
- | To manually load translations from VuFind®' | + | Lokalise is currently set up to automatically update via webhooks when GitHub receives a push. |
+ | |||
+ | However, if you wish to manually load translations from VuFind®' | ||
- Log in to Lokalise and go to the GitHub app page within the site. | - Log in to Lokalise and go to the GitHub app page within the site. | ||
- | - Double-check that the following pull options are set to ON (and all other options are OFF): | + | |
- | * Replace \n with line break | + | - First instance: |
- | * Differentiate keys by file | + | |
- | * Cleanup mode | + | * Replace \n with line break |
- | - Click "Pull now" | + | * Differentiate keys by file |
+ | * Cleanup mode | ||
+ | - Click "Pull now" | ||
+ | - This will pull all *new* translation tokens into Lokalise | ||
+ | | ||
+ | - Double-check that the following pull options are set to ON (and all other options are OFF): | ||
+ | * Replace \n with line break | ||
+ | * Differentiate keys by file | ||
+ | * Replace modified values | ||
+ | | ||
+ | - This will pull changed translations into Lokalise | ||
+ | |||
+ | :!: Note that if new translation files are being added on Github these need to be added to the imported files, Lokalise does not do that on its own. To add new files from the GitHub app settings, click " | ||
+ | |||
+ | Note that language mappings for both Github instances need to be identical (e.g. Basque and Basque(Spain), | ||
Note that it may take a few minutes for processing to complete. | Note that it may take a few minutes for processing to complete. |
development/architecture/localization/lokalise.1695304045.txt.gz · Last modified: 2023/09/21 13:47 by demiankatz