Re: [josm-dev] Translation discussions

It's more the admin that wants to set up a new system :) My impression is that most translators are not JOSM developers. That might be one reason why there is nearly no feedback. You need a copy of the source code tree to find the SVN revision a string was committed in. In the commit message

Re: [josm-dev] Translation discussions

If the JOSM devs really want to move away from launchpad, surely the choice should be between an existing service (transifex and others) or running (and potentially improving if there are missing features) an existing system (for example Pootle) and not wasting effort on yet another ..

Re: [josm-dev] Translation discussions

This is something clearly missing. It is a 10-year old Launchpad bug: https://bugs.launchpad.net/launchpad/+bug/25 2015-10-20 11:21 GMT+02:00 Dirk Stöcker : > On Sun, 18 Oct 2015, Holger Mappt wrote: > > would be good, I think Transifex supports that. Dirk, do you

Re: [josm-dev] Translation discussions

On Sun, 18 Oct 2015, Holger Mappt wrote: would be good, I think Transifex supports that. Dirk, do you still work on a Trac based system? Will it support translation discussions? To be able to discuss the source string would be good too. A little. It's still my goal. I hope I have some time

[josm-dev] Translation discussions

Hi, There are sometimes strings used in the JOSM source, the presets, or a plugin that are hard to translate. What is the preferred way to discuss the translation of such strings? If the origin in the code should be changed then the JOSM tickets can be used. But what about the translation