|
1 | 1 | Vitro-languages |
2 | 2 | =============== |
3 | 3 |
|
4 | | -Files that enable Vitro (and by extension, VIVO) to operate in languages beyond American English. |
| 4 | +Files required for displaying the Vitro (and by extension, VIVO) user interface |
| 5 | +in different natural languages, including American English. |
5 | 6 |
|
6 | 7 | Available language files |
7 | 8 | ------------------------ |
8 | 9 |
|
9 | | -At present, VIVO has been translated into German, Spanish, and Portuguese. You may find the relevant files for each language by searching for files containing _de_DE, _es, and _pt_BR respectively. English uses the prefix _en_US. |
| 10 | +At present, Vitro has been translated into American English (en_US), |
| 11 | +Canadian English (en_CA), Canadian French (fr_CA), German (de_DE), |
| 12 | +Spanish (es), and Brazilian Portuguese (pt_BR). Each available |
| 13 | +language has its own top-level directory in this repository. |
10 | 14 |
|
11 | 15 | Using the language files |
12 | 16 | ------------------------ |
13 | 17 |
|
14 | | -If the files you want already exist here, you can add them to your VIVO instance by |
15 | | -following the instructions in the VIVO wiki for [Adding a language to VIVO][1]. |
| 18 | +If a directory for a language you want to use already exists here, you can |
| 19 | +enable this language in your Vitro/VIVO instance by following the instructions |
| 20 | +in the VIVO wiki for [Adding a language to VIVO][1]. |
16 | 21 |
|
17 | | -If the files for your desired language do not exist then you may use the files in this repository as a |
18 | | -starting point for doing the translations yourself. Search for the required files for any of the language prefixes above (e.g. _en_US), copy the files, and rename your new files using the appropriate language code [prefix][2]. Please send a note to [the VIVO Tech group][3] |
19 | | -to find out if someone else is already working on a translation. |
| 22 | +If a directory for your desired language does not exist, you may copy one of |
| 23 | +the existing directories in this repository to use as a starting point for |
| 24 | +doing the translations yourself. Rename your new directory using the appropriate |
| 25 | +language code [prefix][2], and also rename the files within the various |
| 26 | +levels of subdirectories to end with the appropriate code. Please send a note |
| 27 | +to [the VIVO Tech group][3] to find out if someone else is already working on a |
| 28 | +translation. Additional information about developing a new translation is |
| 29 | +available on the wiki at [Developing a New Interface Language for VIVO][4]. |
20 | 30 |
|
21 | | -If you create a translation, please consider contributing your language files to the VIVO community. |
| 31 | +If you create a translation, please consider contributing your language files to |
| 32 | +the VIVO community. |
22 | 33 |
|
23 | | -[1]: https://wiki.duraspace.org/display/VIVODOC110x/Internationalization#Internationalization-AddinganexistinglanguagetoyourVIVOsite |
| 34 | +[1]: https://wiki.duraspace.org/display/VIVODOC112x/Internationalization#Internationalization-AddinganexistinglanguagetoyourVIVOsite |
24 | 35 | [2]: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes |
25 | 36 | [3]: mailto:vivo-tech@googlegroups.com |
| 37 | +[4]: https://wiki.lyrasis.org/display/VIVODOC112x/Developing+a+New+Interface+Language+for+VIVO |
0 commit comments