Difference between revisions of "Multilingual design principles"
| Line 8: | Line 8: | ||
* Both the [[Glossary#User interface|user interface]] and the [[Glossary#Database content|database content]] should be capable of existing in multiple languages | * Both the [[Glossary#User interface|user interface]] and the [[Glossary#Database content|database content]] should be capable of existing in multiple languages | ||
* Users should be able to switch the [[Glossary#User interface|user interface]] to their preferred language | * Users should be able to switch the [[Glossary#User interface|user interface]] to their preferred language | ||
| − | * When switching the [[Glossary#User interface|interface]] to a preferred language, [[Glossary#Database content|database content]] should also switch, if a translation is available; if not, the content remains in the | + | * When switching the [[Glossary#User interface|interface]] to a preferred language, [[Glossary#Database content|database content]] should also switch, if a translation is available; if not, the content remains in the source language |
| − | * Users with [[Glossary#Translator|translator]] [[Glossary#Access privilege|access privileges]] should be able to contribute translations of [[Glossary#User interface|interface]] elements and descriptions from the | + | * Users with [[Glossary#Translator|translator]] [[Glossary#Access privilege|access privileges]] should be able to contribute translations of [[Glossary#User interface|interface]] elements and descriptions from the source language to any of the [[Glossary#Supported language|supported languages]] |
* [[Glossary#Administrator|Administrators]] should be able to remove languages that are not needed in their application; they should be able to easily add back [[Glossary#Supported language|supported languages]] that were removed | * [[Glossary#Administrator|Administrators]] should be able to remove languages that are not needed in their application; they should be able to easily add back [[Glossary#Supported language|supported languages]] that were removed | ||
* Over time, it should be easy to add new languages to the [[Glossary#Supported language|supported languages]] | * Over time, it should be easy to add new languages to the [[Glossary#Supported language|supported languages]] | ||
| − | When installing ICA-AtoM, the [[Glossary#Administrator|administrator]] specifies the [[Glossary#Default | + | When installing ICA-AtoM, the [[Glossary#Administrator|administrator]] specifies the [[Glossary#Default language|default language]]. Any user can switch the [[Glossary#Current language|current language]] to display the [[Glossary#User interface|user interface]] and [[Glossary#Database content|database content]] in any of the other [[Glossary#Supported language|supported languages]]. |
<div class="note"> | <div class="note"> | ||
Revision as of 23:19, 15 June 2010
Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.
Main Page > User manual > UM-5 Translate content / interface > UM-5.1 Design principles
ICA-AtoM is a multilingual application which incorporates the following design principles:
- Both the user interface and the database content should be capable of existing in multiple languages
- Users should be able to switch the user interface to their preferred language
- When switching the interface to a preferred language, database content should also switch, if a translation is available; if not, the content remains in the source language
- Users with translator access privileges should be able to contribute translations of interface elements and descriptions from the source language to any of the supported languages
- Administrators should be able to remove languages that are not needed in their application; they should be able to easily add back supported languages that were removed
- Over time, it should be easy to add new languages to the supported languages
When installing ICA-AtoM, the administrator specifies the default language. Any user can switch the current language to display the user interface and database content in any of the other supported languages.
ICA-AtoM makes no attempt to automatically generate "translations" from one language to another. It is up to individual translators to do the translations. ICA-AtoM does not "do" translation, rather it supports the activities of translators by providing a structure in which users can contribute translations of descriptions and link these back to the originals.
Known issues
All users with translator access privileges can add or edit translations of both user interface elements and database content in any of the supported languages. In future releases, translator access privileges should be limited by both language and type of translation; for example, a translator may be restricted to translating only database content into only one language.
There is currently no way for system administrators to add new languages to ICA-AtoM via normal web-browser interaction. New languages can only be added by programmers working directly with the code. In future releases, administrators will be able to add new languages to those supported by their application and to make their translations of the user interface available to the wider community of ICA-AtoM users.