Changes between Version 2 and Version 3 of i18n

Timestamp:

Jul 18, 2007, 6:22:26 AM (17 years ago)

Author:

ticheler

Comment:

--

i18n

@@ -59 +59 @@
  - It is pretty trivial to generate a list of i18n_keys in use in the software.
  - The generated output can be used to highlight missing and obsolete keys in each language file.
- - There is the potential to store all keys and language strings in a database that has a simple translation user interface accessible through the web. Such translation mechanism has already been implemented in !GeoNetwork opensource for the non-static strings in the system. It could be setup on the developer website to work as the central translation facility. The static files required for a release can be generated as language packages automatically and be stored in SVN.
+ - There is the potential to store all keys and language strings in a database that has a simple translation user interface accessible through the web. Such translation mechanism has already been implemented in !GeoNetwork opensource for the non-static strings in the system. It could be setup on the developer website to work as the central translation facility. The static files required for a release can be generated as language packages automatically and be stored in SVN. It would require an import function to merge new strings in and flag missing ones. It would also need an XSL based export function to generate the appropriate output files.