Changes between Version 7 and Version 8 of HowToTranslate

Timestamp:

03/26/09 01:02:24 (4 years ago)

Author:

iburago

Comment:

--

HowToTranslate

@@ -1 @@
-== How-to translate GeoNetwork? ==
+= How to translate GeoNetwork =
 
-This how-to describes steps necessary to add a new language support into existing GeoNetwork installation.
+This page describes steps necessary to include support of language other than
+pre-installed into existing instance of GeoNetwork and it's configuration
+components.
 
 
-=== Translation of the user interface ===
+== Translation of the user interface ==
 
-All you need to create new language is following:
- * Create new record in `languages` table in your GeoNetwork's database.
- * In all tables which name ends with `Des` copy all entries marked `en`
-   (or any other language) to entries with new language code.
-   Then you will be able to edit these fields using Web-interface.
+Follow next steps to create new language.
+ * Create new record in `Languages` table in GeoNetwork's database with new
+   language's two-letter code.
+ * In tables which name ends with `Des` copy all entries marked `en` (or any
+   other existing language) to entries with new language code. After that it's
+   possible to edit these fields using Web-interface.
  * Copy folders (all paths listed from GeoNetwork's root folder) to folders
-   with new language code. (You can use any language as base for translation, not only English.)
+   with new language code. (Any existing language could be treated as base for
+   translation, not only English.) Then change copied values with translated
+   strings, of course.
     * User interface
        * `web/geonetwork/loc/en`,
        * `web/intermap/loc/en`.
-    * Metadata standards::
+    * Metadata standards
        * `web/geonetwork/xml/schemas/dublin-core/loc/en`,
        * `web/geonetwork/xml/schemas/fgdc-std/loc/en`,
        * `web/geonetwork/xml/schemas/iso19115/loc/en`,
        * `web/geonetwork/xml/schemas/iso19139/loc/en`.
-
-   Copy also profile specific folders if you're running sandboxes like Bluenet, GéoSource or geocat.ch.
-   Then you should change copied values with translated strings, of course.
- * In ''all'' files `web/geonetwork/loc/`''<language code>''`/strings.xml`
-   add tags with new language's code and it's name. These string will be
-   used by GeoNetwork to indicate current language in interface switcher.
-   For example, adding Russian language identified by `ru` in GeoNetwork,
-   include into those files string `<ru>Русский</ru>`.
-   Here `ru` is the code for Russian language and `Русский` is the Russian
-   language name ''on Russian''.
- * Add new language link in the banner at the main page.
-   Open `web/geonetwork/xsl/banner.xsl` for editing and find this code:
+    * Profile specific folders of sandboxes like Bluenet, GéoSource
+      or geocat.ch.
+ * In ''all'' files `web/geonetwork/loc/`''<language code>''`/strings.xml` add
+   tags with new language's code and it's name. These string used by GeoNetwork
+   to list languages in interface switcher and indicate current a current one.
+   For example, while adding Russian language identified by `ru`, it's necessary
+   to include into those files `<ru>Русский</ru>` line. Here `ru` is the code
+   for Russian and `Русский` is the Russian name ''on Russian''.
+ * Add new language's link in interface switcher banner at the main page.
+   Open `web/geonetwork/xsl/banner.xsl` for editing and find code:
    {{{
    <xsl:choose>
@@ -43 +46 @@
    </xsl:choose>
    }}}
-   Duplicate this fragment (separating new from old using '|') and change `en` to the code of language you're adding.
+   Duplicate this fragment (separating new from old using '`|`') and change `en`
+   to the code of new language.
 
 
-=== Propose your translation for integration into trunk ===
+=== Propose translation for integration ===
 
 You can choose one of these two ways:
  * Create a patch if your are familiar with SVN.
  * Create a ZIP archive with all needed files:
-    * all `loc` directories,
-    * localized database content (use [[http://druid.sourceforge.net/ Druid]] to export as DDF file tables which names ends with `Des`).
+    * all `loc` directories with translated strings,
+    * localized database content (use [[http://druid.sourceforge.net/ Druid]]
+      to export tables which names ends with `Des` as DDF files).
 
-Once done, send the translation to the devel mailing list and/or create a ticket on trac with files attached.
+Once done, send the translation to the `devel` mailing list and/or create a
+ticket on `trac` with files attached.
 
 
-=== Translate GAST ===
+== Translate GAST ==
 
 Files to localize:
@@ -64 +70 @@
 
 
-=== Translate the installer ===
+== Translate the installer ==
 
 The only file to localize is
@@ -70 +76 @@
 
 
-=== Translate the documentation ===
+== Translate the documentation ==
 
 Documentation is located in