Changes between Version 7 and Version 8 of HowToTranslate


Ignore:
Timestamp:
Mar 26, 2009, 1:02:24 AM (15 years ago)
Author:
iburago
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HowToTranslate

    v7 v8  
    1 == How-to translate GeoNetwork? ==
     1= How to translate GeoNetwork =
    22
    3 This how-to describes steps necessary to add a new language support into existing GeoNetwork installation.
     3This page describes steps necessary to include support of language other than
     4pre-installed into existing instance of GeoNetwork and it's configuration
     5components.
    46
    57
    6 === Translation of the user interface ===
     8== Translation of the user interface ==
    79
    8 All you need to create new language is following:
    9  * Create new record in `languages` table in your GeoNetwork's database.
    10  * In all tables which name ends with `Des` copy all entries marked `en`
    11    (or any other language) to entries with new language code.
    12    Then you will be able to edit these fields using Web-interface.
     10Follow next steps to create new language.
     11 * Create new record in `Languages` table in GeoNetwork's database with new
     12   language's two-letter code.
     13 * In tables which name ends with `Des` copy all entries marked `en` (or any
     14   other existing language) to entries with new language code. After that it's
     15   possible to edit these fields using Web-interface.
    1316 * Copy folders (all paths listed from GeoNetwork's root folder) to folders
    14    with new language code. (You can use any language as base for translation, not only English.)
     17   with new language code. (Any existing language could be treated as base for
     18   translation, not only English.) Then change copied values with translated
     19   strings, of course.
    1520    * User interface
    1621       * `web/geonetwork/loc/en`,
    1722       * `web/intermap/loc/en`.
    18     * Metadata standards::
     23    * Metadata standards
    1924       * `web/geonetwork/xml/schemas/dublin-core/loc/en`,
    2025       * `web/geonetwork/xml/schemas/fgdc-std/loc/en`,
    2126       * `web/geonetwork/xml/schemas/iso19115/loc/en`,
    2227       * `web/geonetwork/xml/schemas/iso19139/loc/en`.
    23 
    24    Copy also profile specific folders if you're running sandboxes like Bluenet, GéoSource or geocat.ch.
    25    Then you should change copied values with translated strings, of course.
    26  * In ''all'' files `web/geonetwork/loc/`''<language code>''`/strings.xml`
    27    add tags with new language's code and it's name. These string will be
    28    used by GeoNetwork to indicate current language in interface switcher.
    29    For example, adding Russian language identified by `ru` in GeoNetwork,
    30    include into those files string `<ru>Русский</ru>`.
    31    Here `ru` is the code for Russian language and `Русский` is the Russian
    32    language name ''on Russian''.
    33  * Add new language link in the banner at the main page.
    34    Open `web/geonetwork/xsl/banner.xsl` for editing and find this code:
     28    * Profile specific folders of sandboxes like Bluenet, GéoSource
     29      or geocat.ch.
     30 * In ''all'' files `web/geonetwork/loc/`''<language code>''`/strings.xml` add
     31   tags with new language's code and it's name. These string used by GeoNetwork
     32   to list languages in interface switcher and indicate current a current one.
     33   For example, while adding Russian language identified by `ru`, it's necessary
     34   to include into those files `<ru>Русский</ru>` line. Here `ru` is the code
     35   for Russian and `Русский` is the Russian name ''on Russian''.
     36 * Add new language's link in interface switcher banner at the main page.
     37   Open `web/geonetwork/xsl/banner.xsl` for editing and find code:
    3538   {{{
    3639   <xsl:choose>
    … …  
    4346   </xsl:choose>
    4447   }}}
    45    Duplicate this fragment (separating new from old using '|') and change `en` to the code of language you're adding.
     48   Duplicate this fragment (separating new from old using '`|`') and change `en`
     49   to the code of new language.
    4650
    4751
    48 === Propose your translation for integration into trunk ===
     52=== Propose translation for integration ===
    4953
    5054You can choose one of these two ways:
    5155 * Create a patch if your are familiar with SVN.
    5256 * Create a ZIP archive with all needed files:
    53     * all `loc` directories,
    54     * localized database content (use [[http://druid.sourceforge.net/ Druid]] to export as DDF file tables which names ends with `Des`).
     57    * all `loc` directories with translated strings,
     58    * localized database content (use [[http://druid.sourceforge.net/ Druid]]
     59      to export tables which names ends with `Des` as DDF files).
    5560
    56 Once done, send the translation to the devel mailing list and/or create a ticket on trac with files attached.
     61Once done, send the translation to the `devel` mailing list and/or create a
     62ticket on `trac` with files attached.
    5763
    5864
    59 === Translate GAST ===
     65== Translate GAST ==
    6066
    6167Files to localize:
    … …  
    6470
    6571
    66 === Translate the installer ===
     72== Translate the installer ==
    6773
    6874The only file to localize is
    … …  
    7076
    7177
    72 === Translate the documentation ===
     78== Translate the documentation ==
    7379
    7480Documentation is located in