The GeoNetwork opensource geospatial catalog v2.2.0 is out!
Document Actions
Translating the application
This How-to applies to: 2.0.0
Translation of the user interface is usualy the first thing people can assist with. This howto explains how to do this most effectively.
Translation of the user interface is usualy the first thing people can assist with (and we really appreciate them!). In order to do this effectively, we suggest to take the following approach:
<abstract>Abstract</abstract>
in Spanish:
<abstract>Resumen</abstract>
- Provide translations towards the end of the development cycle, when we move to producing a Release Candidate for a version of the software. This will avoid spending much time on checking the original English files for changes that should be reflected in the translated files.
- Use the original language files as provided in the CVS system. These source code versions contain variables that are replaced with custom values during the installation process.
- The strings.xml file contains most of the GUI strings, while the others mainly contain descriptions of metadata standard fields, error messages and some other messages. These are updated less frequently than the strings.xml file.
- When translating, try to keep the translations as close as possible to the English original and try to restrict the length of the strings to a reasonable size compared to the original.
- Translate only the strings inside the XML tags. Do not translate the tags themselves!
<abstract>Abstract</abstract>
in Spanish:
<abstract>Resumen</abstract>
- You can send translations directly to one of the project administrators
by
Admin
—
last modified
2007-03-14 01:59
Creative Commons - http://creativecommons.org/licenses/by/2.5/
