Re: [josm-dev] i18n for release

2016-04-28 Thread Paul Hartmann
On 28.04.2016 11:05, Dirk Stöcker wrote: On Tue, 26 Apr 2016, Paul Hartmann wrote: what are the required steps for i18n update before a release? Is it enough to do the following? $ cd josm/i18n $ ant updatecore $ svn ci ../core Yes. That's one of the possibilities. Great, that's a whole

[OSM-dev] iD news: v1.9.3 release and participation in Google Summer of Code

2016-04-28 Thread Bryan Housel
Hi, OSM! Just wanted to announce a few things about the iD editor project.. iD 1.9.3 was released Monday 4/25/16 and is now available for editing on openstreetmap.org . The release includes: - easy draggable imagery offset adjustment control (built by Kushan Joshi) -

[josm-dev] JOSM mailinglist and DKIM

2016-04-28 Thread Dirk Stöcker
Hello, the josm-mailinglist destroys DKIM signatures, as each messages gets [josm-dev] added to the subject and that breaks any signature. To get rid of that effect I'll turn off adding [josm-dev] in the subject in a few days. As the mailinglist software adds enough information to a

Re: [josm-dev] JOSM question

2016-04-28 Thread Dirk Stöcker
On Tue, 26 Apr 2016, EthnicFood IsGreat wrote: I have a custom paint style that I use. Recently I changed the name of my style. Now in the JOSM preferences, display settings, colors, my custom colors are duplicated—they are all listed under my old style name, and also all listed under my new

Re: [josm-dev] i18n for release

2016-04-28 Thread Dirk Stöcker
On Tue, 26 Apr 2016, Paul Hartmann wrote: what are the required steps for i18n update before a release? Is it enough to do the following? $ cd josm/i18n $ ant updatecore $ svn ci ../core Yes. That's one of the possibilities. Ciao -- http://www.dstoecker.eu/ (PGP key available)

Re: [OSM-dev] libosmium and missing multipolygons

2016-04-28 Thread Jochen Topf
On Thu, Apr 21, 2016 at 04:48:26PM +0200, Jochen Topf wrote: > There are a few known bugs in the libosmium MP code and I am working on an > improved versions which will be ready soon. At the moment I would suggest, you > wait a few days and then try the new code, before digging further into this.