|
1 | | -This project provides lists of various ISO standards (e.g. country, |
2 | | -language, language scripts, and currency names) in one place, rather |
3 | | -than repeated in many programs throughout the system. |
| 1 | +This project provides lists of various ISO standards (e.g. country, language, |
| 2 | +language scripts, and currency names) in one place, rather than repeated in many |
| 3 | +programs throughout the system. |
4 | 4 |
|
5 | | -Currently there are lists of languages and countries embedded in |
6 | | -several different programs, which leads to dozens of lists of |
7 | | -200 languages, translated into more than 90 languages ... not |
8 | | -very efficient. |
| 5 | +Currently there are lists of languages and countries embedded in several |
| 6 | +different programs, which leads to dozens of lists of 200 languages, translated |
| 7 | +into more than 90 languages ... not very efficient. |
9 | 8 |
|
10 | | -With this project, we create a single "gettext domain" for every |
11 | | -supported ISO standard which contains the translations of |
12 | | -that domain. It is easy for a programmer to re-use those |
13 | | -translations instead of maintaining their own translation |
14 | | -infrastructure. Moreover, the programmer does not need to follow |
15 | | -changes in the ISO standard and will not work with outdated |
16 | | -information. |
| 9 | +With this project, we create a single "gettext domain" for every supported ISO |
| 10 | +standard which contains the translations of that domain. It is easy for a |
| 11 | +programmer to re-use those translations instead of maintaining their own |
| 12 | +translation infrastructure. Moreover, the programmer does not need to follow |
| 13 | +changes in the ISO standard and will not work with outdated information. |
0 commit comments