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.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
development:architecture:localization [2020/09/22 13:28] – demiankatz | development: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 [[# | + | - Create a new language file as described [[# |
- 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/ | + | If you need to customize the language files residing in VUFIND_HOME/ |
Starting with VuFind 2.5, you can also put a languages directory inside a [[development: | Starting with VuFind 2.5, you can also put a languages directory inside a [[development: |
development/architecture/localization.txt · Last modified: 2024/01/10 13:56 by demiankatz