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 revision
Previous revision
Next revisionBoth sides next revision
development:architecture:localization [2020/09/22 14:23] demiankatzdevelopment:architecture:localization [2022/08/02 15:18] demiankatz
Line 9: Line 9:
 ===== Translate Function ===== ===== Translate Function =====
  
-VuFind uses Zend Framework'translation mechanism.  The translator object is registered in the service manager as 'VuFind\Translator'.+VuFind uses Laminas' translation mechanism.  The translator object is registered in the service manager under the standard 'Laminas\Mvc\I18n\Translator' key.
  
 Notes: Notes:
Line 43: Line 43:
   - Edit [[configuration:files: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.
  
 +==== Updating a Language ====
 +
 +If you wish to maintain an existing set of language files, but you are not sure which strings have been recently added, VuFind includes a language tool which will generate lists of missing strings in all supported languages. To access it, turn on [[development:troubleshooting#turn_on_development_mode|development mode]] and then add "/DevTools/Language" to the end of your base URL to access the language report.
 +
 +Note also that there are [[administration:command_line_utilities#language_category|language-related command line utilities]] which can help with common maintenance tasks. Most importantly, rather than manually sorting your language files, you can add new/missing strings to the ends, and rely upon the "language normalize" tool to put everything in correct order and format files to project standards.
  
 ==== Customizing Language Files ==== ==== Customizing Language Files ====
Line 132: Line 137:
 VuFind's help screens contain too much text for the standard translation mechanism to be a practical way of presenting them in multiple languages.  Instead, under the theme/root/templates/HelpTranslations directory, the help templates are in folders whose names correspond with VuFind language codes (i.e. "en" for English).  When a user requests a help screen, VuFind attempts to serve them the most appropriate version for their selected language, though it defaults to the English version if nothing else is available; as of this writing, help screens have not been translated into all possible languages. VuFind's help screens contain too much text for the standard translation mechanism to be a practical way of presenting them in multiple languages.  Instead, under the theme/root/templates/HelpTranslations directory, the help templates are in folders whose names correspond with VuFind language codes (i.e. "en" for English).  When a user requests a help screen, VuFind attempts to serve them the most appropriate version for their selected language, though it defaults to the English version if nothing else is available; as of this writing, help screens have not been translated into all possible languages.
  
 +===== Video =====
 +
 +This topic is discussed in the [[videos:i18n|Internationalization]] video.
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
development/architecture/localization.txt · Last modified: 2024/01/10 13:56 by demiankatz