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 revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
evergreen-admin:customizations:i18n [2012/06/27 11:31]
kivilahtio
evergreen-admin:customizations:i18n [2012/10/29 07:49]
kivilahtio [Build environment]
Line 30: Line 30:
 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): <br />+**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)   * 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   * 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
-<​sub>​-kivilahtio 27.6.2012</​sub>​ 
  
 ===Inserting the strings into the database=== ===Inserting the strings into the database===
Line 42: Line 41:
 #   * 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.
evergreen-admin/customizations/i18n.txt · Last modified: 2018/06/05 11:06 by sandbergja

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.