Changes between Version 183 and Version 184 of TaggingPresets
- Timestamp:
- 2021-05-07T02:58:06+02:00 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TaggingPresets
v183 v184 63 63 ==== Comments ==== 64 64 <!-- this is an example comment -->:: 65 The document can contain embedded comments. 65 The document can contain embedded comments. 66 66 \\ 67 67 68 68 ==== Preset group creation ==== 69 69 <group>:: 70 Used to group items in sub menus. `name` is required, `icon` is optional attribute. 70 Used to group items in sub menus. `name=""` is required, `icon=""` is optional attribute. 71 71 <item>:: 72 Every item is one annotation set to select from. `name` is required, `type` and `preset_name_label` are recommended, `icon`, `name_template` and `match_expression` are optional attributes. 72 Every item is one annotation set to select from. `name=""` is required, `type=""` and `preset_name_label=""` are recommended, `icon=""`, `name_template=""` and `match_expression=""` are optional attributes. 73 73 <separator />:: 74 Insert a line separator into the menu. 74 Insert a line separator into the menu. 75 75 \\ 76 76 77 77 ==== Preset window layout ==== 78 78 <label />:: 79 Labels are static texts for display. `text` is a required attribute, `icon` and `icon_size` are optional. 79 Labels are static texts for display. `text=""` is a required attribute, `icon=""` and `icon_size=""` are optional. 80 80 <space />:: 81 Add some space (i.e. a newline). 81 Add some space (i.e. a newline). 82 82 <optional>:: 83 Used to group some optional elements of an item. The `text` attribute is optional. If used without `text` then this is equivalent to `<space /><label text="Optional Attributes:" /><space />` 83 Used to group some optional elements of an item. The `text=""` attribute is optional. If used without `text=""` then this is equivalent to `<space /><label text="Optional Attributes:" /><space />` 84 84 <item_separator />:: 85 Add a horizontal separator line between items. 85 Add a horizontal separator line between items. 86 86 <link />:: 87 Specify a web link for this feature or to anything else of use. Either the `wiki` (referring to an OSM wiki page, e.g. `"Tag:leisure=park"`) or the `href` (full URL) attribute is required. When the `wiki` attribute is used the link points to the wiki page of the language JOSM is set to. If it doesn't exist the English page is shown. 87 Specify a web link for this feature or to anything else of use. Either the `wiki=""` (referring to an OSM wiki page, e.g. `"Tag:leisure=park"`) or the `href=""` (full URL) attribute is required. When the `wiki=""` attribute is used the link points to the wiki page of the language JOSM is set to. If it doesn't exist the English page is shown. 88 88 <checkgroup>:: 89 To group checks. The `columns` attribute is required. 89 To group checks. The `columns=""` attribute is required. 90 90 <roles>:: 91 This is required around `<role />` and adds the heading ("Available roles role count elements") to the table which is generated by several `<role />`. 91 This is required around `<role />` and adds the heading ("Available roles role count elements") to the table which is generated by several `<role />`. 92 92 <role />:: 93 To specify possible roles of members in relations. The `key` attribute is required, `text`, `requisite`, `count `, `type` and `member_expression` are optional.93 To specify possible roles of members in relations. The `key=""` attribute is required, `text=""`, `requisite=""`, `count=""`, `type=""` and `member_expression=""` are optional. 94 94 <preset_link />:: 95 Adds a link to an other preset with a label on top. The `preset_name` attribute is required, `text` to override the label (default is `"Edit also …"`) and `text_context` are optional. A sequence of `<preset_link />` without `text` or a identical `text` value are grouped below one label. \\ 96 **Watch out** for presets with identical **`name`** as it is not predictable to which preset the link will lead to, see #12716. \\ 97 Having the same tag in both presets does not work, see #18992. \\ 98 Using `<preset_link />` in presets opened from [wikitr:/Help/Dialog/RelationEditor relation editor] produces unexpected changes, see #19392. 95 Adds a link to an other preset with a label on top. The `preset_name=""` attribute is required, `text=""` to override the label (default is `"Edit also …"`) and `text_context=""` are optional. A sequence of `<preset_link />` without `text=""` or a identical `text=""` value are grouped below one label. \\ 96 **Watch out** for presets with identical **`name=""`** as it is not predictable to which preset the link will lead to, see #12716. \\ 97 Having the same tag in both presets does not work, see #18992. \\ 98 Using `<preset_link />` in presets opened from [wikitr:/Help/Dialog/RelationEditor relation editor] produces unexpected changes, see #19392. 99 99 \\ 100 100 101 101 ==== Set a fixed key value pair ==== 102 102 <key />:: 103 This tag will always set a key to a specific value. `key` is required and if `value` is present, the key will be set. If `value` attribute is omitted, the key is removed. The `match` attribute is optional. 103 This tag will always set a key to a specific value. `key=""` is required and if `value=""` is present, the key will be set. If `value=""` attribute is omitted, the key is removed. The `match=""` attribute is optional. 104 104 \\ 105 105 106 106 ==== Attribute entry and selection dialog boxes ====#EntrySelectionBoxes 107 107 <text />:: 108 A text edit field to enter any arbitrary string from the user. `key` is mandatory, `text `, `default`, `use_last_as_default`, `auto_increment`, `length`, `alternative_autocomplete_keys`, `match`, `icon` and `icon_size` (both since r17605) are optional.108 A text edit field to enter any arbitrary string from the user. `key=""` is mandatory, `text=""`, `default=""`, `use_last_as_default=""`, `auto_increment=""`, `length=""`, `alternative_autocomplete_keys=""`, `match=""`, `icon=""` and `icon_size=""` (both since r17605) are optional. 109 109 <combo />:: 110 Displays a multiple choice combo box. `key ` and `values` are mandatory, `text`, `default`, `editable`, `delimiter`, `values_from`, `display_values`, `short_descriptions`, `use_last_as_default`, `values_searchable`, `length`, `values_no_i18n`, `values_sort`, `match`, `icon` and `icon_size` (both since r17605) are optional.\\111 If `editable ` is `"true"` (default), combo boxes can be edited as if they were text fields (additional to the drop down menu). Non editable combo boxes can only contain one of the specified values.\\112 If the key is `colour` or `colour:*` or `*:colour`, a color preview and color picker is added on the right (see #8352). 110 Displays a multiple choice combo box. `key=""` and `values=""` are mandatory, `text=""`, `default=""`, `editable=""`, `delimiter=""`, `values_from=""`, `display_values=""`, `short_descriptions=""`, `use_last_as_default=""`, `values_searchable=""`, `length=""`, `values_no_i18n=""`, `values_sort=""`, `match=""`, `icon=""` and `icon_size=""` (both since r17605) are optional.\\ 111 If `editable=""` is `true` (default), combo boxes can be edited as if they were text fields (additional to the drop down menu). Non editable combo boxes can only contain one of the specified values.\\ 112 If the key is `colour` or `colour:*` or `*:colour`, a color preview and color picker is added on the right (see #8352). 113 113 [=#multiselect] 114 114 <multiselect />:: 115 Displays a list from which zero or more items can be chosen. `key ` and `values` are mandatory, and `text`, `default`, `delimiter`, `values_from`, `rows`, `display_values`, `short_descriptions`, `use_last_as_default`, `values_searchable`, `values_no_i18n`, `values_sort`, `match`, `icon` and `icon_size` (both since r17605) are optional. The selected values will be concatenated with the specified delimiter (default: semicolon) and written to the tag value. If a tag value has already been set when the preset dialog is opened, the `<multiselect />` will attempt to mark the appropriate items in the list as select. If the tag value cannot be represented by a combination of choices in the list, then the list will be disabled so that the user cannot accidentally overwrite a custom value. In contrast to the `<combo />` element, the `<multiselect />` expects the list of values, descriptions etc. to use the specified delimiter, i.e. by default you will have to use a semicolon. You can specify `delimiter=","` but then a comma will also be used in the tag value.115 Displays a list from which zero or more items can be chosen. `key=""` and `values=""` are mandatory, and `text=""`, `default=""`, `delimiter=""`, `values_from=""`, `rows=""`, `display_values=""`, `short_descriptions=""`, `use_last_as_default=""`, `values_searchable=""`, `values_no_i18n=""`, `values_sort=""`, `match=""`, `icon=""` and `icon_size=""` (both since r17605) are optional. The selected values will be concatenated with the specified delimiter (default: semicolon, `;`) and written to the tag value. If a tag value has already been set when the preset dialog is opened, the `<multiselect />` will attempt to mark the appropriate items in the list as select. If the tag value cannot be represented by a combination of choices in the list, then the list will be disabled so that the user cannot accidentally overwrite a custom value. In contrast to the `<combo />` element, the `<multiselect />` expects the list of values, descriptions etc. to use the specified delimiter, i.e. by default you will have to use a semicolon. You can specify `delimiter=","` but then a comma will also be used in the tag value. 116 116 <list_entry />:: 117 Used in `<combo>` and `<multiselect>`. More information see `short_descriptions `[#short_description below]. The attributes are `value`, `display_value`, `short_description`, `icon` and `icon_size`.117 Used in `<combo>` and `<multiselect>`. More information see `short_descriptions=""`, [#short_description below]. The attributes are `value=""`, `display_value=""`, `short_description=""`, `icon=""` and `icon_size=""`. 118 118 <check />:: 119 A checkbox which the user can select, deselect or set as unset. The `key` attribute is mandatory. `text `, `default`, `match`, `value_on` , `value_off`, `disable_off`, `icon` and `icon_size` (both since r15437) are optional.119 A checkbox which the user can select, deselect or set as unset. The `key=""` attribute is mandatory. `text=""`, `default=""`, `match=""`, `value_on=""` , `value_off=""`, `disable_off=""`, `icon=""` and `icon_size=""` (both since r15437) are optional. 120 120 \\ 121 121 122 122 ==== Templates ==== 123 123 <chunk>:: 124 To define a template of elements for later (repeated) use. The `id` attribute is mandatory. 124 To define a template of elements for later (repeated) use. The `id=""` attribute is mandatory. 125 125 <reference>:: 126 To include an earlier defined template. The `ref` attribute is mandatory. 126 To include an earlier defined template. The `ref=""` attribute is mandatory. 127 127 \\ 128 128 … … 130 130 The attributes of the tags have the following meaning: 131 131 name="a_name":: 132 Specify a name for an item. This name will be used in the GUI to display the tagging preset. 132 Specify a name for an item. This name will be used in the GUI to display the tagging preset. 133 133 name_context="context":: 134 Translation context for name attribute to separate equals words with different meaning (not required for in-file translations). 134 Translation context for name attribute to separate equals words with different meaning (not required for in-file translations). 135 135 type="data_type":: 136 When specified, only objects of the given type will work with this tagging preset. Can be `"node"`, `"way"`, `"closedway"`, `"multipolygon"`, `"relation"` or any comma separated combination of them. Note that `"multipolygon"` is not included in `"relation"`, so if the preset should apply for multipolygons and other relation types, you need to specify both: `"multipolygon,relation"`. Also used in the `<role>` tag to specify which object types are allowed for a specific relation member. 136 When specified, only objects of the given type will work with this tagging preset. Can be `"node"`, `"way"`, `"closedway"`, `"multipolygon"`, `"relation"` or any comma separated combination of them. Note that `"multipolygon"` is not included in `"relation"`, so if the preset should apply for multipolygons and other relation types, you need to specify both: `"multipolygon,relation"`. Also used in the `<role>` tag to specify which object types are allowed for a specific relation member. 137 137 icon="iconname":: 138 A name or link to an icon. The image will be used as icon to display in the selection list and when adding the preset to the toolbar. Icons can also be used in `<item>`, `<label />`, plus all [#EntrySelectionBoxes attribute entry and selection dialog boxes] (since r17605, before it was only `<list_entry />` and `<check />`). It is placed in front of `<text />` The icon should be quadratic in size. See [wikitr:/Styles#Iconhandling Icon handling] how icons can be specified. 138 A name or link to an icon. The image will be used as icon to display in the selection list and when adding the preset to the toolbar. Icons can also be used in `<item>`, `<label />`, plus all [#EntrySelectionBoxes attribute entry and selection dialog boxes] (since r17605, before it was only `<list_entry />` and `<check />`). It is placed in front of `<text />` The icon should be quadratic in size. See [wikitr:/Styles#Iconhandling Icon handling] how icons can be specified. 139 139 icon_size="a number":: 140 The maximal size of an icon in px. If no value is given, default is 16 for `<label />` and the default icon size for `<list_entry />` (in `<combo>` and `<multiselect>`). 140 The maximal size of an icon in px. If no value is given, default is 16 for `<label />` and the default icon size for `<list_entry />` (in `<combo>` and `<multiselect>`). 141 141 key="some_key":: 142 This specifies the property key that will be modified by the item. In case of `<role>` it is the role name used in a relation. 142 This specifies the property key that will be modified by the item. In case of `<role>` it is the role name used in a relation. 143 143 text="Any text":: 144 The description, that will be displayed before the gui element, (in case of `<check />` after the gui element and the optional icon). Also used for `<label>` and `<optional>`. 144 The description, that will be displayed before the gui element, (in case of `<check />` after the gui element and the optional icon). Also used for `<label>` and `<optional>`. 145 145 text_context="context":: 146 Translation context for text attribute to separate equals words with different meaning (not required for in-file translations). 146 Translation context for text attribute to separate equals words with different meaning (not required for in-file translations). 147 147 default="default_value":: 148 An explicitly declared default value for the item. This value is ''only'' applied through a preset when the object the preset is applied to has ''zero keys''. 148 An explicitly declared default value for the item. This value is ''only'' applied through a preset when the object the preset is applied to has ''zero keys''. 149 149 If no value for default is specified, no value is set to the key. Used in `<check />`, `<text />`, `<combo />` and `<multiselect />`. For `<check />` only the values `"on"` and `"off"` are valid. 150 150 values="entry1,entry2,entry3":: 151 A list of entries (for the `<combo />` box and `<multiselect />`). The list has to be separated by commas (for the combo box) or by the specified delimiter (for the multiselect). If a value contains the delimiter, the delimiter may be escaped with a backslash. If a value contains a backslash, it must also be escaped with a backslash. 151 A list of entries (for the `<combo />` box and `<multiselect />`). The list has to be separated by commas (for the combo box) or by the specified delimiter (for the multiselect). If a value contains the delimiter, the delimiter may be escaped with a backslash. If a value contains a backslash, it must also be escaped with a backslash. 152 152 values_from="JAVA code":: 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". 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". 154 154 values_no_i18n="true|false":: 155 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. 155 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. 156 156 values_sort="true|false":: 157 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"`.\\ 158 Users can globally disable sorting with the preference key `taggingpreset.sortvalues`. 157 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"`.\\ 158 Users can globally disable sorting with the preference key `taggingpreset.sortvalues`. 159 159 values_context="context":: 160 Translation context for values attribute to separate equals words with different meaning (not required for in-file translations). 160 Translation context for values attribute to separate equals words with different meaning (not required for in-file translations). 161 161 display_values="Entry1,Entry2,Entry3":: 162 A list of entries that is displayed to the user. Must be the same number and order of entries as `values ` and `editable` must be `"false"` or not specified. For the delimiter character and escaping, see the remarks at `values`. Used in `<combo />` and `<multiselect />`.162 A list of entries that is displayed to the user. Must be the same number and order of entries as `values=""` and `editable=""` must be `"false"` or not specified. For the delimiter character and escaping, see the remarks at `values=""`. Used in `<combo />` and `<multiselect />`. 163 163 value="foobar":: 164 Specify a value to be entered in the `<key>` tag. 164 Specify a value to be entered in the `<key>` tag. 165 165 value_on="foobar":: 166 Specify the true value to be entered in the `<key>` tag of a checked `<check />` (default is `"yes"`). 166 Specify the true value to be entered in the `<key>` tag of a checked `<check />` (default is `"yes"`). 167 167 value_off="foobar":: 168 Specify the false value to be entered in the `<key>` tag of a unchecked `<check />` (default is `"no"`). 168 Specify the false value to be entered in the `<key>` tag of a unchecked `<check />` (default is `"no"`). 169 169 disable_off="true":: 170 Whether the off value of a `<check />` is disabled in the dialog, i.e., only unset or `"yes"` are provided. 170 Whether the off value of a `<check />` is disabled in the dialog, i.e., only unset or `"yes"` are provided. 171 171 editable="false":: 172 The combo box is read only, which means that the user can only select an item in the list. Default is `"true"`, which means, the user can add other values as text. **Feature is broken see #6157**. 172 The combo box is read only, which means that the user can only select an item in the list. Default is `"true"`, which means, the user can add other values as text. **Feature is broken, see #6157**. 173 173 use_last_as_default="true|false|force":: 174 For `<combo />`, `<multiselect />` or `<text />` fields the last used value is used as default. Using `"force"` enforces this behavior also for already tagged objects. Default is `"false"`. 174 For `<combo />`, `<multiselect />` or `<text />` fields the last used value is used as default. Using `"force"` enforces this behavior also for already tagged objects. Default is `"false"`. 175 175 rows="count":: 176 Specify the number of rows to display in `<multiselect />` entry (if not set, it is auto determined by java or the look and feel and results in e.g. 8). Currently, you need to add one additional row to display all values, see #19013. 176 Specify the number of rows to display in `<multiselect />` entry (if not set, it is auto determined by java or the look and feel and results in e.g. 8). Currently, you need to add one additional row to display all values, see #19013. 177 177 name_template="template", name_template_filter="search expression":: 178 Custom name formatter for osm primitives matching this preset. See below [[#name_templatedetails]] fordetails.178 Custom name formatter for osm primitives matching this preset. See [#name_templatedetails name template details] below. 179 179 match="none|key|key!|keyvalue|keyvalue!":: 180 Allows to change the matching process, i.e., determining whether the tags of an OSM object fit into this preset. If a preset fits then it is linked in the [wikitr:/Help/Dialog/TagsMembership Tags/Membership dialog]. 181 * `none`: neutral, i.e., do not consider this item for matching 182 * `key`: positive if key matches, neutral otherwise 183 * `key!`: positive if key matches, negative otherwise 184 * `keyvalue`: positive if key and value matches, neutral otherwise 185 * `keyvalue!`: positive if key and value matches, negative otherwise \\ 186 **Note**: For a match, at least one positive and no negative is required. Default is `"keyvalue!"` for `<key>` and `"none"` for `<text />`, `<combo />`, `<multiselect />` and `<check />`. 187 match_expression=" anexpression"::188 additional criteria for matching primitives, specified in [wikitr:/Help/Action/Search JOSM search] syntax. ''(since r17662)'' \\ 189 For instance, a preset with `match_expression="foo=bar"` requires OSM objects to have the tag `foo=bar`. You may want to use the `match_expression=""` to exclude certain OSM objects, e.g. when a more specific preset is present. 180 Allows to change the matching process, i.e., determining whether the tags of an OSM object fit into this preset. If a preset fits then it is linked in the [wikitr:/Help/Dialog/TagsMembership Tags/Membership dialog]. 181 * `none`: neutral, i.e., do not consider this item for matching 182 * `key`: positive if key matches, neutral otherwise 183 * `key!`: positive if key matches, negative otherwise 184 * `keyvalue`: positive if key and value matches, neutral otherwise 185 * `keyvalue!`: positive if key and value matches, negative otherwise \\ 186 **Note**: For a match, at least one positive and no negative is required. Default is `"keyvalue!"` for `<key>` and `"none"` for `<text />`, `<combo />`, `<multiselect />` and `<check />`. 187 match_expression="search expression":: 188 additional criteria for matching primitives, specified in [wikitr:/Help/Action/Search JOSM search] syntax. ''(since r17662)'' \\ 189 For instance, a preset with `match_expression="foo=bar"` requires OSM objects to have the tag `foo=bar`. You may want to use the `match_expression=""` to exclude certain OSM objects, e.g. when a more specific preset is present. 190 190 id="unique_identifier":: 191 the unique identifier for this `<chunk>` 191 the unique identifier for this `<chunk>` 192 192 ref="unique_identifier":: 193 the unique identifier of the (already defined) template to include 193 the unique identifier of the (already defined) template to include 194 194 columns="a number":: 195 the number of columns of grouped `<check />` 195 the number of columns of grouped `<check />` 196 196 requisite="optional|required":: 197 If a relation member is optional or required. Default is `"optional"`. 197 If a relation member is optional or required. Default is `"optional"`. 198 198 count="a number":: 199 How often can a role occur (if not given unlimited number is assumed) 200 member_expression=" anexpression"::201 an expression, in [wikitr:/Help/Action/Search JOSM search] syntax, for objects of this role 199 How often can a role occur (if not given unlimited number is assumed) 200 member_expression="search expression":: 201 an expression, in [wikitr:/Help/Action/Search JOSM search] syntax, for objects of this role 202 202 regexp="true":: 203 set to `"true"` if the key of a role is a regular expression. This allows variable roles e.g. `<role key="level_-?\d+" text="Building level" regexp="true" requisite="optional" type="relation" />` allows the roles `level_0`, `level_1`,... 203 set to `"true"` if the key of a role is a regular expression. \\ 204 This allows variable roles e.g. `<role key="level_-?\d+" text="Building level" regexp="true" requisite="optional" type="relation" />` allows the roles `level_0`, `level_1`,... 204 205 preset_name="exact_name":: 205 The exact name of the preset to link to. 206 The exact name of the preset to link to. 206 207 preset_name_label="false|true":: 207 Whether to insert "[preset name]" label in dialog (defaults to `"false"` for backward-compatibility on external presets). 208 Whether to insert "[preset name]" label in dialog (defaults to `"false"` for backward-compatibility on external presets). 208 209 length="a number":: 209 The length of a `<text />` or `<combo />` box (number of characters allowed). 210 The length of a `<text />` or `<combo />` box (number of characters allowed). 210 211 alternative_autocomplete_keys="some_key(s)":: 211 A comma separated list of alternative keys to use for auto completion of `<text>`. 212 A comma separated list of alternative keys to use for auto completion of `<text>`. 212 213 auto_increment="-2,-1,+1,+2":: 213 May contain a comma separated list of integer increments or decrements, e.g. `"-2,-1,+1,+2"`. A button will be shown next to the `<text />` field for each value, allowing the user to select auto-increment with the given stepping. Auto-increment only happens if the user selects it. There is also a button to deselect auto-increment. Default is no auto-increment. Mutually exclusive with `use_last_as_default`. 214 May contain a comma separated list of integer increments or decrements, e.g. `"-2,-1,+1,+2"`. A button will be shown next to the `<text />` field for each value, allowing the user to select auto-increment with the given stepping. Auto-increment only happens if the user selects it. There is also a button to deselect auto-increment. Default is no auto-increment. Mutually exclusive with `use_last_as_default=""`. 214 215 delimiter="special character":: 215 The character that separates values. In case of `<combo />` the default is ''comma''. In case of `<multiselect />` the default is ''semicolon'' and this will also be used to separate selected values in the tag. More information see `<multiselect />` [#multiselect above]. 216 The character that separates values. In case of `<combo />` the default is ''comma'' (`,`). In case of `<multiselect />` the default is ''semicolon'' (`;`) and this will also be used to separate selected values in the tag. More information see `<multiselect />`, [#multiselect above]. 216 217 [=#short_description] 217 218 short_descriptions="Entry1,Entry2,Entry3":: 218 A delimiter-separated list of texts to be displayed below each `display_value`. (Only if it is not possible to describe the entry in 2-3 words.) Instead of a comma separated list using `values`, `display_values` and `short_descriptions`, the following form is also supported: `<list_entry value="" display_value="" short_description="" icon="" icon_size="" />` 219 A delimiter-separated list of texts to be displayed below each `display_value=""`. (Only if it is not possible to describe the entry in 2-3 words.) Instead of a comma separated list using `values=""`, `display_values=""` and `short_descriptions=""`, the following form is also supported: \\ 220 `<list_entry value="" display_value="" short_description="" icon="" icon_size="" />` 219 221 values_searchable="true|false":: 220 Whether to search in `<combo />` or `<multiselect />` `(display_)values` when searching for presets. 221 value_template="...":: 222 A template to generate the value automatically based on other `<text />` values of this preset. ''(since r17639)'' \\ For instance, `"Bus {ref}: {from} → {to}"` can be used to generate the name of a bus route relation. 222 Whether to search in `values=""` and `display_values=""`, respectively, `value=""` and `display_value=""` of `<combo />` or `<multiselect />` searching for presets. 223 value_template="template":: 224 A template to generate the value automatically based on other tag values of the object. The syntax of `name_template=""` is use, [#NameTemplateSyntax see below]. ''(since r17639)'' \\ 225 For instance, `"Bus {ref}: {from} → {to}"` can be used to generate the name of a bus route relation. 223 226 \\ 224 227 … … 248 251 \\ 249 252 250 ====== Syntax ====== 253 ====== Syntax ======#NameTemplateSyntax 251 254 * `{var}` - use value of variable var 252 * `?{condition1 'value1' | condition2 'value2 | 'value3'}` - use value1 if condition1 is satisfied, value3 isno condition is satisfied. Condition can be either explicit -the same expression as in search or filters is used- or implicit; the value is used when all variables used inside exist255 * `?{condition1 'value1' | condition2 'value2 | 'value3'}` - use ''value1'' if ''condition1'' is satisfied, ''value3'' if no condition is satisfied. Condition can be either explicit - in [wikitr:/Help/Action/Search JOSM search] syntax - or implicit; the value is used when all variables used inside exist 253 256 * `!{search_expression 'template'}` - search_expression is evaluated and first matching primitive is used as context for template. Useful for example to get tags of parent relation. 254 257 \\ … … 267 270 268 271 delete_if_empty="true":: 269 was removed in r5155. You can simply remove this attribute if still used in your preset. 272 was removed in r5155. You can simply remove this attribute if still used in your preset. 270 273 required="true":: 271 replaced by `match` since r5155 274 replaced by `match=""` since r5155 272 275 \\ 273 276 274 277 == Translation == 275 To support translations, all textual elements (`name `, `text`, `display_values`) may also be localized. E.g. `de.name` would represent the name in case the German language support is loaded. In the preset code the English term must be the first before possible translations are added.276 277 In JOSM internally ([source:josm/trunk/resources/data/defaultpresets.xml internal preset]) all `name `, `text` and `display_values` are translated when no specific translation has been given in XML file. When no `display_values` are supplied, then `values` will be treated as `display_values` and translated instead. When translations of equal words but different meanings may conflict, a translation context should be specified. Use `name_context`, `text_context` or `values_context` for this. The context should be a meaningful short description to help translators.278 To support translations, all textual elements (`name=""`, `text=""`, `display_values=""`) may also be localized. E.g. `de.name=""` would represent the name in case the German language support is loaded. In the preset code the English term must be the first before possible translations are added. 279 280 In JOSM internally ([source:josm/trunk/resources/data/defaultpresets.xml internal preset]) all `name=""`, `text=""` and `display_values=""` are translated when no specific translation has been given in XML file. When no `display_values=""` are supplied, then `values=""` will be treated as `display_values=""` and translated instead. When translations of equal words but different meanings may conflict, a translation context should be specified. Use `name_context=""`, `text_context=""` or `values_context=""` for this. The context should be a meaningful short description to help translators. 278 281 279 282 The translation for the internal preset is done at [https://translations.launchpad.net/josm/trunk Launchpad] (and will probably change to another service in the future, since the Launchpad web interface often produces timeout errors, see #8645).
