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.
development:architecture:localization

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
development:architecture:localization [2020/09/22 13:28] demiankatzdevelopment:architecture:localization [2020/09/22 14:23] demiankatz
Line 38: Line 38:
 ==== Adding a New Language ==== ==== Adding a New Language ====
  
-  - Create a new language file as described [[#formatting language files|above]] and put it in the languages directory (either in the root of VuFind if you are planning to commit the new language to the master branch, or inside your [[configuration:local_settings_directory|local settings directory]] if this is a local customization).+  - Create a new language file as described [[#formatting language files|above]] and put it in the languages directory (either in the root of VuFind if you are planning to commit the new language to the dev branch, or inside your [[configuration:local_settings_directory|local settings directory]] if this is a local customization).
   - If you also wish to translate strings inside text domains (see below) you will need to create appropriate subdirectories inside languages, and put additional language files inside these directories.   - If you also wish to translate strings inside text domains (see below) you will need to create appropriate subdirectories inside languages, and put additional language files inside these directories.
   - If desired, translate help screens as described [[#help screen translation|above]].   - If desired, translate help screens as described [[#help screen translation|above]].
Line 46: Line 46:
 ==== Customizing Language Files ==== ==== Customizing Language Files ====
  
-If you need to customize the language files residing in VUFIND_HOME/languages but do not want to commit this customization to the master branch, you only need to create a languages folder in your local folder (or any folder that is configured as your VUFIND_LOCAL_DIR). Any language file in your VUFIND_LOCAL_DIR/languages folder will be merged with its corresponding language file in VUFIND_HOME/languages (implicit inheritance).+If you need to customize the language files residing in VUFIND_HOME/languages but do not want to commit this customization to the dev branch, you only need to create a languages folder in your local folder (or any folder that is configured as your VUFIND_LOCAL_DIR). Any language file in your VUFIND_LOCAL_DIR/languages folder will be merged with its corresponding language file in VUFIND_HOME/languages (implicit inheritance).
  
 Starting with VuFind 2.5, you can also put a languages directory inside a [[development:architecture:user_interface|theme]] folder to apply custom translations to that specific theme. This can be useful, for example, to use shorter strings in a mobile interface than a desktop version. Starting with VuFind 2.5, you can also put a languages directory inside a [[development:architecture:user_interface|theme]] folder to apply custom translations to that specific theme. This can be useful, for example, to use shorter strings in a mobile interface than a desktop version.
development/architecture/localization.txt · Last modified: 2024/01/10 13:56 by demiankatz