About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
legacy:vufind_1.x_developer_manual:language_localization_support

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
Last revisionBoth sides next revision
legacy:vufind_1.x_developer_manual:language_localization_support [2015/12/11 19:36] – ↷ Page moved from language_localization_support to legacy:vufind_1.x_developer_manual:language_localization_support demiankatzlegacy:vufind_1.x_developer_manual:language_localization_support [2015/12/21 16:47] – ↷ Links adapted because of a move operation demiankatz
Line 12: Line 12:
  
   * If you attempt to translate a string that is not found in a language map, the original string will be displayed untranslated.   * If you attempt to translate a string that is not found in a language map, the original string will be displayed untranslated.
-  * If you turn debug on in [[config.ini]], a special marker will be shown around untranslated strings to help track down missing translations in the code.+  * If you turn debug on in [[configuration:files:config.ini]], a special marker will be shown around untranslated strings to help track down missing translations in the code.
   * Many of the translated strings in the language files are simply chunks of English text.  However, more recent additions are represented as shorter tokens (i.e. "adv_search_filters").  The token approach is often preferable since it allows for more concise map files and reduces the chances of conflicts where the same text has multiple meanings.   * Many of the translated strings in the language files are simply chunks of English text.  However, more recent additions are represented as shorter tokens (i.e. "adv_search_filters").  The token approach is often preferable since it allows for more concise map files and reduces the chances of conflicts where the same text has multiple meanings.
  
Line 35: Line 35:
   - Create a new language file as described [[#formatting language files|above]] and put it in the web/lang directory.   - Create a new language file as described [[#formatting language files|above]] and put it in the web/lang directory.
   - If desired, translate help screens as described [[#help screen translation|above]].   - If desired, translate help screens as described [[#help screen translation|above]].
-  - Edit [[config.ini]] and add your new language to the [Languages] section.+  - Edit [[configuration:files:config.ini]] and add your new language to the [Languages] section.
 ---- struct data ---- ---- struct data ----
 ---- ----
  
legacy/vufind_1.x_developer_manual/language_localization_support.txt · Last modified: 2018/12/19 14:19 by demiankatz