Changes between Version 180 and Version 181 of TaggingPresets

Timestamp:

2021-04-26T20:49:51+02:00 (5 years ago)

Author:

skyper

Comment:

no need for values_no_i18n with only numerical values

TaggingPresets

@@ -153 +153 @@
   To use instead of `values` if the list of values has to be obtained with a Java method of this form: `public static String[] getValues()`; The value must be: "full.package.name.ClassName#methodName".
  values_no_i18n="true|false"::
-  Disables internationalisation for value to avoid mistakes, see #11696. Default is `"false"`. Used in `<combo />` and `<multiselect />`. (Useful e.g. for opening hours or brand names.)
- values_sort="false"::
+  Disables internationalisation for values to avoid mistakes, see #11696. Default is `"false"`. Used in `<combo />` and `<multiselect />`. (Useful e.g. for keys `opening hours` or `brand`.) Not needed with keys with only numbers as values like `layer` or `level` which are already excluded from translation.
+ values_sort="true|false"::
   Values of `<combo />` and `<multiselect />` are sorted alphabetic in every language. With this attribute you can disable the alphabetic sorting if the values should keep the given order, see #5509 and #11926. (In the JOSM internal preset this is used e.g. for the keys `tracktype`, `direction`, `network`, `smoothness`, `visibility` or `trail_visibility`.) Default is `"true"`.\\
  Users can globally disable sorting with the preference key `taggingpreset.sortvalues`.