Steve, did some final test with r3730 after merging the branch back to trunk (just Windows build, but as I start mkgmap on linux and windows in unicode environment I do not expect any problems): still all ok... Thanks again. Patrik On 14.12.2016 21:01, Patrik Brunner wrote:
Steve, In very short: all looks fine.
Bit longer: I've cleaned up the building environment and created a small map (LUX) a few times:
* on linux, unicode * on linux, cp1252 * on windows, unicode * on windows, cp1252
I've checked these results the following ways:
* gmap archive (jmc_cli) on BaseCamp * gmapsupp.img directly on the GPS (Oregon 450t only) * gmapsupp.img in BaseCamp while having GPS connected to PC
And as said at the very beginning: all looks fine.
As you know: only some Latin1 characters where tested, but I do not think we'll have new conceptual problems with other characters.
I would consider the issue as solved, I'm a very happy user and from my side (pure user perspective) it's ready to be merged.
Many thanks for your support on this, really appreciated. Patrik
On 14.12.2016 17:51, Steve Ratcliffe wrote:
Patrik
In short: All looks fine right now, I could not find/create/produce any strange behaviours...
That is great to hear. I shall wait for you final tests before merging.
I also encourage others to test out as well as there are a fair few changes.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev