Presets translation state list

[kocio]

Is it possible to make automatically refreshed list of all the presets with their translations? It would make translating this part of the application easier if one can spot all the missing/broken strings. I think presets are very important for users, so their full and current translation should be also an important thing. Of course external presets might also have some interface and similar list for translating them.

[Don-vip]

Have you tried tagging preset tester plugin?

[anonymous]

No, I didn't know it, but now I can't make it run in JOSM, nor in the standalone mode:

$ java -jar tagging-preset-tester.jar
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError: org/openstreetmap/josm/gui/tagging/TaggingPreset$PresetPanel

at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
at java.lang.Class.getMethod0(Class.java:3018)
at java.lang.Class.getMethod(Class.java:1784)
at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526)

Caused by: java.lang.ClassNotFoundException: org.openstreetmap.josm.gui.tagging.TaggingPreset$PresetPanel

at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 7 more

I even don't know what it really does and how could it be helpful with managing all the presets translations (with their options), because I can't find any closer description:

​http://wiki.openstreetmap.org/wiki/JOSM/Plugins/tagging-preset-tester
https://josm.openstreetmap.de/wiki/TaggingPresetTester

[Don-vip]

The plugin works fine from JOSM, please update and try again.
The plugin helps you to vizualize quickly the presets, I think it should meet your need.

[Klumbumbus]

I do not really understand this ticket. For internal presets the translation is done at Launchpad. You can view there untranslated items. For external presets until now you need in file translation by the author. But there is some work going on to include also external presets into launchpad translation system, see #11392.

[Klumbumbus]

How do you start tagging presets tester after installtion in JOSM?

[kocio]

@Klumbumbus: The problem is that the code for translating is already very big - in Polish we have 81% now and I don't know when those remaining 19% will be done, because it's a lot of work and not that visible for users. What I would like to have then is a kind of filter just for translating presets, because they are constantly changing (probably adding new ones or new options) and people use them a lot. Maybe just separation them to file like "josm_presets-xx.po" would do? Maybe also separation of other messages classes ("josm_menu-xx.po"?) would be possible to make managing the translation easier.

I run JOSM v8491 then in the menu Okna (Windows) there is the second item called Tagging Preset Tester, but clicking it has no effect, also the key combination Ctrl+Shift+Alt+T doesn't show anything. I started JOSM from the console, but I don't see any trace of this actions either.

[Klumbumbus]

Replying to kocio:

I run JOSM v8491 then in the menu Okna (Windows)

Ah ok. Its description was misleading. see #11571

(for me this plugin works fine)

[Klumbumbus]

Replying to kocio:

@Klumbumbus: The problem is that the code for translating is already very big - in Polish we have 81% now and I don't know when those remaining 19% will be done, because it's a lot of work and not that visible for users. What I would like to have then is a kind of filter just for translating presets, because they are constantly changing (probably adding new ones or new options) and people use them a lot. Maybe just separation them to file like "josm_presets-xx.po" would do? Maybe also separation of other messages classes ("josm_menu-xx.po"?) would be possible to make managing the translation easier.

Hm. Maybe you can follow (e.g. RSS feed) the changes at https://josm.openstreetmap.de/log/josm/?verbose=on. Normally the change description gives you a hint if it is translation related or not.

Or you ask the polish community to translate the remaining 2640 strings. 30 persons, everyone 88 strings. Should be possible :) Once you are at 100% it is easier to keep up with the changes.

[stoecker]

Or you ask the polish community to translate the remaining 2640 strings. 30 persons, everyone 88 strings. Should be possible :) Once you are at 100% it is easier to keep up with the changes.

There have been 0 to 100% 1 person in 2 days, so that's definitely possible.

[anonymous]

The more I translate (and over the years it's more than 20 projects I guess), the more I'm aware how hard is it to make a good, useful translation. This is a GIS project, so there's a lot of things I have no clue about (or just what are polish GIS terminology) and prefer not to make it just for the sake of completeness. Tuning the presets so they have the right meaning for polish audience is hard and it may take months, because in many cases I have not only to find the right wording I could use, but also if it's not already used in a different context (like "way", which may be used for some roads, but we already use it mainly for GPS traces and geometric primitive).

I'm not nitpicking: we already had real problem with "village green", which was carelessly translated as a "city green" (translator probably was not aware that it's a special kind of green place which is "nawsie" in Polish - and I didn't heard that word until I checked at the Wikipedia), so it's better when the mappers have the best translation possible.

There are projects which separates UI, server, client, web and alike modules for translation and it really makes it easier. Currently the translation file alone has almost 2 MB (!), so I still feel it would good to chop it a bit.

[stoecker]

Well, I developed most of the translation infrastructure and did also major parts of German translation and I know how complicated it is. Thought we already have a very relaxed policy aceppting 2000 strings for inclusion. Many projects accept only 100%.

No, we wont split it more than we do now. The I18n directory creates three files for JOSM, JOSM-server and plugins, but this is not done for the translation upload. There only the order is kept, so that core is in front. You can use special translation tools instead of Launchpad, they'll allow you to search and select what you want.

Anyway my goal is not to encourage anything beside 100%!

[kocio]

OK, I understand - I think we can close this issue then (as WONTFIX probably).

However if anybody could give me a hint how to restrict the view of untranslated strings to just presets-related strings or (even better) how to be automatically informed that there are such strings waiting for translation, I would appreciate it a lot!

BTW: my original plan was to make it 100% in Polish, but I gave up (for the reasons explained above) and nobody else seems to be translating it. I still hope one day it will be just uploading current additions, but I doubt I can achieve it alone.

[stoecker]

Three ways I know:

• Download the po file from Launchpad and use a translation tool like KBabel which has pretty good functions. Search for texts in trans_presets... file (I don't know how easy this is, it's long time since I last used that tool). After translating reupload the po file.
• Download the po file from launchpad and and search for trans_presets, start, search for "" and translate missing text. Upload po file afterwards
• With Launchpad: Click on the missing strings and jump forward until you find a preset related text. The others are on the pages before or after.