Plugin Translations
===================

Run from plugin main directory:
ant pot
ant poimport
ant pomerge
ant lang

Detailed Version
----------------
* To kick off the translation of the plugin it is SVN committed.
  After a day the translatable strings are visible at Launchpad
  (https://translations.launchpad.net/josm/trunk/+pots/josm).
* After the Java code or the plugin description in build.xml was
  changed, you need to run "ant pot".  That creates/updates the
  template file po/plugin.pot.
* Download the latest translations from Launchpad and copy them into
  the directory po with "ant poimport".  This uses the version that is
  updated once a day.  For a more recent version you need to request a
  download from
  https://translations.launchpad.net/josm/trunk/+pots/josm/+export.
  Then run "ant -Dpoimport.tarball=URL poimport", replace URL with the
  translation download URL.
* Remove all untranslated strings and other translations with
  "ant pomerge".
* Create the language files in the data directory with "ant lang".
* SVN commit plugin changes, SVN update plugin directory, run
  "ant dist" to create a new plugin release, SVN commit new plugin
  release (../../dist/plugin.jar).  "ant dist" will add the
  translations of the plugin description to the manifest.

Additions to plugin build.xml:
    <!-- ** internationalization ** -->
    <import file="i18n/build-i18n.xml"/>
    <target name="additional-manifest">
        <antcall target="mftrans"/>
    </target>

Global Run
----------
From the global i18n directory the steps are:
./launchpad bzronly
ant -Dplugin=plugin singleplugintrans

* The command "launchpad bzronly" exports the latest revision of the
  Launchpas translations.
* "ant singleplugintrans" generates the language files in the plugin
  data directory.  Then it deletes to PO files.
* It is not possible to add the translations of the plugin description
  to the manifest.