27;t meant for single plugin translation. It joins all
the files into one large translation file (or 3 files).
Your easiest choice probably is to call gettext commandline tool manually:
find ../plugins/plugname -iname "*.java" |xargs xgettext -k -ktrc:1c,2
-kmarktrc:1c,2 -ktr -kmarktr
Hello,
Could someone give me 101 on how in the world I'll be able to create
working .pot files (which then could go into the GitHub repo and into
Transifex from there if I so need in the future) and .lang files from there?
The i18n directory isn't meant for single plugin translation
Good afternoon list!
I was trying to get translation for my plugins started but I seem to be
unable to perform the most basic task of creating a .pot :/
Going by
https://josm.openstreetmap.de/wiki/DevelopersGuide/DevelopingPlugins#Translatingaplugin
I thought of using option b) and use ant in jos
On Thu, 26 Dec 2013, Holger Mappt wrote:
I18N is already complete as it is now. What can be done is only a
cleaner interface by storing data at the right place, but it is a lot of
work and no user visible result. And probably some side-effects nobody
knows yet.
You mean the plugin descript
On 25.12.2013 13:56, Dirk Stöcker wrote:
How should changing the commons file help you to add other languages?
I'm not sure if I understand your question. The only thing that is left
to do is to add the translations of the plugin description to the plugin
MANIFEST.
plugins/build-common.xm
On Tue, 24 Dec 2013, Holger Mappt wrote:
Actually, it's just plugins/build-common.xml that needs to be changed. I
would not change plugins that don't use that file. It's most beneficial for
new plugins anyway.
How should changing the commons file help you to add other languages?
While pla
On 24.12.2013 13:12, Dirk Stöcker wrote:
The build.xml generates the manifest. To add translations to the
manifest, the build.xml file must be changed to add or remove these
lines. That is not so easy, as the build.xml files still do not follow a
common style (although we try to unify them).
A
On Mon, 23 Dec 2013, Holger Mappt wrote:
It's amazing how much details there are. I will look into the MANIFEST
translation update. What do you mean with "automatic changes to the
build.xml"? The file build.xml is changed automatically or something should
be added to build.xml that changes t
On 22.12.2013 13:19, Dirk Stöcker wrote:
On Sat, 21 Dec 2013, Holger Mappt wrote:
I copy the development.jar in the JOSM plugin directory
(~/.josm/plugins) and JOSM extracts some data like the icon. It
doesn't extract the translation (yet) if the plugin is not
installed
You need to supply th
On Sat, 21 Dec 2013, Holger Mappt wrote:
The plugin descriptions are part of the official JOSM after the plugin is
ready and released. But I want to test everything including the translations
*before* I release the plugin. I copy the development.jar in the JOSM plugin
directory (~/.josm/plug
On 20.12.2013 23:14, Simon Legner wrote:
The plugin descriptions are part of the JOSM core language file since
the plugin descriptions are shown in the plugin list in the preference
dialog. I don't see why one would need them also in the plugin language
file.
The plugin descriptions are part of
On Fri, 20 Dec 2013, Holger Mappt wrote:
ant -Dplugin=gpxfilter singleplugintrans
Ah, thanks. I fixed build.xml to make it work. A plugin is translated with
the commands:
./launchpad.pl bzronly
ant -Dplugin=gpxfilter singleplugintrans
Hmm, my call worked on my machine also. Maybe diffe
On Fri, 20 Dec 2013, Simon Legner wrote:
The plugin descriptions are part of the JOSM core language file since the
plugin descriptions are shown in the plugin list in the preference dialog. I
don't see why one would need them also in the plugin language file.
Well, as plugin author cannot rel
Hi!
On 20/12/13 22:58, Holger Mappt wrote:
The original i18n tasks did not add the plugin description (property
plugin.description in plugin build.xml) to the plugin POT/*.lang files.
I changed that, the plugin description is now part of the plugin
template josm.pot. That translation is used
On 20.12.2013 10:01, Dirk Stöcker wrote:
On Thu, 19 Dec 2013, Holger Mappt wrote:
3a) My first idea was to check out that branch. ... I stopped the "bzr branch
lp:~openstreetmap/josm/josm_trans" operation after 600MB were
downloaded. There is no point in downloading and keeping gigabytes of
On Thu, 19 Dec 2013, Holger Mappt wrote:
3a) My first idea was to check out that branch. Then it is easy to update to
the latest version of the translations. But Bazaar is one of those revision
control systems where you get the complete repository in your working copy.
I stopped the "bzr bra
Hi,
I think I figured this out now. As Simon pointed out, there are
infrequent plugin i18n updates, so you don't need to do anything at all.
But if you want to update the translations of a plugin more frequently:
There is an automatic process that extracts the language strings from
the JOS
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
On 22 Nov 2013 17:24, Simon Legner wrote:
Which plugin are you referring to?
The plugin implements ticket #7712 [1]. It's not yet released.
[1] http://josm.openstreetmap.de/ticket/7712
See
https://trac.openstreetmap.org/browser/subversion/applications/editors/josm/i18n/build.xml#L81
how the
Hi!
Which plugin are you referring to?
On 22/11/13 14:02, Holger Mappt wrote:
But how do I get the translation for the 10 strings of a single plugin?
Is there a description how to get a small subset of the translations?
See
https://trac.openstreetmap.org/browser/subversion/applications/edito
Hi,
JOSM core and all plugins from the JOSM plugins SVN repository are
translated with Launchpad. There is documentation how to to work with
the complete set of strings (some 8000+). But how do I get the
translation for the 10 strings of a single plugin? Is there a
description how to get a
21 matches
Mail list logo