evergreen-admin:customizations:i18n
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
evergreen-admin:customizations:i18n [2011/12/30 18:42] – [Build environment] dbs | evergreen-admin:customizations:i18n [2024/08/25 14:32] (current) – tagging sleary | ||
---|---|---|---|
Line 9: | Line 9: | ||
The translatable strings from the i18n files are being converted to GNU gettext (POT and PO) format for ease of translation. The corresponding tools for converting the files to and from the gettext format and their native format live in the build/i18n/ directory. They require a few supplemental tools over and above the normal Evergreen requirements. | The translatable strings from the i18n files are being converted to GNU gettext (POT and PO) format for ease of translation. The corresponding tools for converting the files to and from the gettext format and their native format live in the build/i18n/ directory. They require a few supplemental tools over and above the normal Evergreen requirements. | ||
===Prerequisites=== | ===Prerequisites=== | ||
- | On Debian, install | + | Install |
- | apt-get install | + | make -f Open-ILS/ |
</ | </ | ||
+ | |||
===Creating or updating a set of PO files for translation=== | ===Creating or updating a set of PO files for translation=== | ||
Line 29: | Line 30: | ||
make LOCALE=fr-CA install</ | make LOCALE=fr-CA install</ | ||
This will automatically update the PO files with the latest definitions from the en-US source POT files, then generate the full set of project files for the requested locale. Any strings that have not been translated, or that are marked as " | This will automatically update the PO files with the latest definitions from the en-US source POT files, then generate the full set of project files for the requested locale. Any strings that have not been translated, or that are marked as " | ||
+ | |||
+ | **NOTE** If you have trouble installing your translated .po-files, make sure you are installing your files in valid gettext-standard PO-format. Things to look for include (but not limited to): | ||
+ | * BOM BOM! Gettext tools do not support BOM (http:// | ||
+ | * Runaway newlines. Some translators like to end their translations to a newline. On each row, msgid and msgstr definitions must have a starting and ending double quote | ||
===Inserting the strings into the database=== | ===Inserting the strings into the database=== | ||
Line 37: | Line 42: | ||
# * username ' | # * username ' | ||
psql -h localhost -U evergreen -f Open-ILS/ | psql -h localhost -U evergreen -f Open-ILS/ | ||
- | |||
**NOTE** This does not copy the correct files into / | **NOTE** This does not copy the correct files into / | ||
+ | **NOTE** If you fail to INSERT your 950.data.seed-values-< | ||
+ | <code sql> | ||
+ | INSERT INTO config.i18n_locale VALUES (' | ||
+ | </ | ||
+ | |||
+ | ===Localizing the TPAC=== | ||
+ | To make your localization visible in the TPAC, you should follow these instructions: | ||
+ | http:// | ||
=====Technical details behind localization===== | =====Technical details behind localization===== | ||
The technical details of how we handle localization in Evergreen - staff client, catalogue, and OpenSRF - have been moved [[backend-devel: | The technical details of how we handle localization in Evergreen - staff client, catalogue, and OpenSRF - have been moved [[backend-devel: | ||
Line 83: | Line 95: | ||
* **Major**: Has inline JavaScript regexes for telephone number, zip code | * **Major**: Has inline JavaScript regexes for telephone number, zip code | ||
+ | |||
+ | {{tag> |
evergreen-admin/customizations/i18n.1325288573.txt.gz · Last modified: 2022/02/10 13:33 (external edit)