Changes between Version 27 and Version 28 of DevelopersGuide/DefaultPresets


Ignore:
Timestamp:
2016-08-21T18:02:56+02:00 (9 years ago)
Author:
openstreetmap.org-user-d1g
Comment:

use heading (linkable)

Legend:

Unmodified
Added
Removed
Modified
  • DevelopersGuide/DefaultPresets

    v27 v28  
    2727* The icon should hide as less as possible in the mapview, so colourful icons with transparent background are preferred over black/white icons with square background.
    2828* The icon should be understandable in all countries.
    29 * Possible problems with svg in JOSM (Please check if the svg file correctly works within JOSM.)
    30  * The base size of svg should be 16px or larger than 64px. Images with a base size between 16 and 64 px will not be scaled down to 16px.
    31  * There are some svg libraries which do not work with JOSM (the images get deformed). If you have such a file try the following workaround: create a new svg document with Inkscape, copy the svg data to this new file, resize the page to the data and save.
    32  * Check the code of the file in a text editor. Search for '''viewBox''' value in the beginning of the file. If the icon is, for example, in 16x16 pixels, and if you made it in Inkscape (at least this happens in 0.91 version) and have defined in Document Properties 16,00000 by 16,00000 pixels, probably in the file code you have these values '''viewBox="0 0 16.000002 16.000001"'''. Change it to '''viewBox="0 0 16 16"''' or you will have problems (see #12201 and the fix [o31865])
    33  * svg icons are automatically cleaned up to reduce file size in the JOSM build. So there is no need to do this step manually before uploading svg files to svn. See comment:35:ticket:10479, comment:10:ticket:10877 and ticket:12201#comment:21 Uncleaned svgs are better for further editing.
    34  * Due to a bug in svgcleaner however, the svg code shouldn't contain arguments starting with special characters in style codes e.g. `-inkscape-font-specification:Sans;`. This can lead to color changes (see #13158).
    35  * If the icon icludes gradients, the offset needs to increase at every stop, i.e. two stops with the same offset are not allowed, see [https://github.com/blackears/svgSalamander/pull/4 svg salamander].
     29=== Possible problems with svg in JOSM ===
     30Please check if the svg file correctly works within JOSM.
     31
     32* The base size of svg should be 16px or larger than 64px. Images with a base size between 16 and 64 px will not be scaled down to 16px.
     33* There are some svg libraries which do not work with JOSM (the images get deformed). If you have such a file try the following workaround: create a new svg document with Inkscape, copy the svg data to this new file, resize the page to the data and save.
     34* Check the code of the file in a text editor. Search for '''viewBox''' value in the beginning of the file. If the icon is, for example, in 16x16 pixels, and if you made it in Inkscape (at least this happens in 0.91 version) and have defined in Document Properties 16,00000 by 16,00000 pixels, probably in the file code you have these values '''viewBox="0 0 16.000002 16.000001"'''. Change it to '''viewBox="0 0 16 16"''' or you will have problems (see #12201 and the fix [o31865])
     35* svg icons are automatically cleaned up to reduce file size in the JOSM build. So there is no need to do this step manually before uploading svg files to svn. See comment:35:ticket:10479, comment:10:ticket:10877 and ticket:12201#comment:21 Uncleaned svgs are better for further editing.
     36* Due to a bug in svgcleaner however, the svg code shouldn't contain arguments starting with special characters in style codes e.g. `-inkscape-font-specification:Sans;`. This can lead to color changes (see #13158).
     37* If the icon icludes gradients, the offset needs to increase at every stop, i.e. two stops with the same offset are not allowed, see [https://github.com/blackears/svgSalamander/pull/4 svg salamander].
    3638
    3739