Difference between revisions of "Multilingual design principles"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
*Both the [[User interface|user interface]] and the [[Database content|database content]] should be capable of existing in multiple languages. | *Both the [[User interface|user interface]] and the [[Database content|database content]] should be capable of existing in multiple languages. | ||
| − | *Users should be able to switch the interface to their | + | *Users should be able to switch the [[User interface|user interface]] to their preferred language. |
| − | *When switching the interface to a [[ | + | *When switching the [[User interface|interface]] to a preferred language, [[Database content|database content]] should also switch, if a translation is available; if not, the content remains in the [[Default source language|default source language]]. |
| − | *Users with [[Translator|translator privileges]] should be able to contribute translations of interface elements and descriptions from the [[Default source language|default source language]] to any of the [[Supported language|supported languages]]. | + | *Users with [[Translator|translator]] [[Access privilege|access privileges]] should be able to contribute translations of [[User interface|interface]] elements and descriptions from the [[Default source language|default source language]] to any of the [[Supported language|supported languages]]. |
| − | *[[Administrator|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. | + | *[[Administrator|Administrators]] should be able to remove languages that are not needed in their application; they should be able to easily add back [[supported language|supported languages]] that were removed. |
*Over time, it should be easy to add new languages to the [[Supported language|supported languages]]. | *Over time, it should be easy to add new languages to the [[Supported language|supported languages]]. | ||
| Line 31: | Line 31: | ||
| − | When installing ICA-AtoM, the | + | When installing ICA-AtoM, the [[Administrator|administrator]] specifies the [[Default source language|default source language]]. Any user can switch [[Language view|language view]] to display the [[User interface|user interface]] and [[Database content|database content]] in any of the other [[Supported language|supported languages]]. |
Revision as of 11:58, 18 July 2008
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.
Design principles
Main Page > (UM) User manual > UM-5 Translate content / interface > UM-5.1 Design principles
ICA-AtoM is a multi-lingual application and 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 default source language.
- Users with translator access privileges should be able to contribute translations of interface elements and descriptions from the default 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.
The current version of ICA-AtoM (v1.0 beta) supports the following languages:
- Dutch
- English
- French
- Portuguese
- Spanish
When installing ICA-AtoM, the administrator specifies the default source language. Any user can switch language view to display the user interface and database content in any of the other supported languages.
Note that 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 (v1.0 beta)
- It is assumed that the original description is always written in the default source language of the application and then subsequently translated into other languages. In fact, in a multi-linguistic system, the originals may be in any number of languages. The only way currently to distinguish the original from the translation is by including a note in the Notes area (archival description) or Control area (authority record, archival institution).
- All users with translator access can add or edit translations of both user interface and database content in any of the supported languages. In future releases, translator access should be limited by both language and type of translation (interface or content); e.g. a translator may be restricted to translating only content into only one language (e.g. French, but not Dutch).
- There is currently no easy way to "see at a glance" what has or has not yet been translated. The current release of ICA-AtoM includes a sub-tab on the Main menu bar for "Translate > New content"; in a future release will list descriptions not yet translated into the user's current 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 interface available to the wider community of ICA-AtoM users.