evergreen-admin:customizations:i18n
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
evergreen-admin:customizations:i18n [2011/12/30 18:42] – [Build environment] dbs | evergreen-admin:customizations:i18n [2012/06/27 11:36] – kivilahtio | ||
---|---|---|---|
Line 29: | Line 29: | ||
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 82: | Line 86: | ||
* Org unit interface: | * Org unit interface: | ||
* **Major**: Has inline JavaScript regexes for telephone number, zip code | * **Major**: Has inline JavaScript regexes for telephone number, zip code | ||
- |
evergreen-admin/customizations/i18n.txt · Last modified: 2023/08/11 10:40 by sandbergja