Hi! On 22/11/13 21:45, Holger Mappt wrote:
I guess I can just commit the plugin and wait until someone triggers the translation process.
That's correct as long as you commit to https://trac.openstreetmap.org/browser/subversion/applications/editors/josm/plugins (instead of GitHub or any other location).
The strings to be translated are extracted automatically every night and pushed to Launchpad.
For the translated strings to be included to your plugin JAR, you can (1) use the i18n/build.xml to do so, (2) ask another JOSM developer, or (3) wait for infrequent plugin "i18n updates".
In my opinion, for (1), the time consuming factor is not the download size, but the time required to process all languages/plugin combinations.
I don't see an SVN commit in i18n/build.xml. Is that done manually? Always or on request only?
The idea is to execute `ant update` which updates all translations for JOSM core and all plugins. Then you repackage your plugin (using `ant dist` in the plugin dir) and commit the plugin JAR and source directory.
What counts as project in this context, JOSM (GPL v2+) or the plugin (more or less any license)?
The link suggests that the plugin itself must be licensed as JOSM since it builds upon JOSM.
Cheers, Simon _______________________________________________ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
