Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds translations for "site" on the candidate_list page (both dropdown and data table) as an example of how to handle database translations.
The text domain of the table name (in the case of sites, the "psc" table) has the options that are translated. This can be placed in the project/locale/$lang/LC_MESSAGES/psc.po file and compiled with
msgfmt -o psc.mo psc.po.I tested this using the following
.pofor raisinbread's sites and Japanese (translations from Google Translate)This is not included in the PR, because the site names are LORIS install specific. I intend to send a different PR with a script to extract a
.potfile from the database values for a table.