User Tools

Site Tools


evergreen-admin:customizations:i18n

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
evergreen-admin:customizations:i18n [2010/01/26 13:15] jamesrfevergreen-admin:customizations:i18n [2023/08/11 10:40] (current) – [Prerequisites] install via the Makefile target sandbergja
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 the translation build tools:<code bash> +Install the translation build tools:<code bash> 
-sudo aptitude install translate-toolkit python-dev python-setuptools python-lxml +make -f Open-ILS/src/extras/Makefile.install <osname>-translator 
-sudo easy_install polib +</code> 
-sudo easy_install simplejson</code>+
  
 ===Creating or updating a set of PO files for translation=== ===Creating or updating a set of PO files for translation===
Line 30: Line 30:
 make LOCALE=fr-CA install</code> make LOCALE=fr-CA install</code>
 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 "fuzzy", will be substituted with the English version of the strings. 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 "fuzzy", will be substituted with the English version of the strings.
 +
 +**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://en.wikipedia.org/wiki/BOM)
 +  * 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 38: Line 42:
 #   * username 'evergreen' #   * username 'evergreen'
 psql -h localhost -U evergreen -f Open-ILS/src/sql/Pg/950.data.seed-values-fr-CA.sql</code> psql -h localhost -U evergreen -f Open-ILS/src/sql/Pg/950.data.seed-values-fr-CA.sql</code>
- 
  
 **NOTE** This does not copy the correct files into /openils/var/web/opac/common/js/<locale>/ **NOTE** This does not copy the correct files into /openils/var/web/opac/common/js/<locale>/
  
 +**NOTE** If you fail to INSERT your 950.data.seed-values-<locale>.sql, you need to add your language definition to config.i18n_locale issuing the following command:
 +<code sql>
 +INSERT INTO config.i18n_locale VALUES ('fi-FI','fin','Suomi','Suomen komia kieli');
 +</code>
 +
 +===Localizing the TPAC===
 +To make your localization visible in the TPAC, you should follow these instructions:
 +http://docs.evergreen-ils.org/2.3/_creating_a_new_skin_the_bare_minimum.html
 =====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:i18n|to a separate page]] to avoid confusing this more practical page. The technical details of how we handle localization in Evergreen - staff client, catalogue, and OpenSRF - have been moved [[backend-devel:i18n|to a separate page]] to avoid confusing this more practical page.
Line 83: Line 94:
   * 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.1264529720.txt.gz · Last modified: 2022/02/10 13:33 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.