Changes between Version 47 and Version 185 of TaggingPresets


Ignore:
Timestamp:
(multiple changes)
Author:
(multiple changes)
Comment:
(multiple changes)

Legend:

Unmodified
Added
Removed
Modified
  • TaggingPresets

    v47 v185  
    1 [[TranslatedPages(outdated=The preset syntax has changed and this page needs to be adjusted to reflect the changes)]]
     1[[TranslatedPages]]
     2[[PageOutline(2-10,Table of Contents)]]
     3
     4''If you want to learn installation steps for presets, see [[JOSMImage(dialogs/propertiesdialog)]] [wikitr:/Help/Preferences/TaggingPresetPreference Tagging Presets] register in [[JOSMImage(preference)]] [wikitr:/Help/Action/Preferences Preferences]'' \\
     5''If you want to use presets or need complete reference of presets see [wikitr:/Presets Presets]''
     6
     7----
     8
    29= Tagging Presets =
    3 JOSM supports distributed tagging presets. This is a XML config file that describes a GUI for entering tags (or properties, annotations, sometimes called map features). The XML files can be placed anywhere in the web or at the users local file system. Presets can be added by the users at a central page [wiki:Presets].
    4 
    5 
    6 == Installing presets ==
    7 Open the [Help/Action/Preferences preferences window], click [[Image(source:trunk/images/preferences/map.png,20)]] map settings and select third tab [Help/Preferences/Map#TaggingPresets "Tagging Presets"].
    8 
    9 ----
    10 
    11 == Develop a new preset – Example ==
    12 
    13 [[Image(tagging_screenshot.png,align=right)]]
     10JOSM supports distributed tagging presets. This is a XML config file that describes a GUI for entering tags (or properties, annotations, sometimes called map features).
     11
     12The presets can be placed anywhere in the web or at the users local file system. JOSM can be configured to use custom local or remote Presets.
     13
     14== Develop a new preset ==
     15The tagging preset description is in a very simple XML format. Details see [#XML below].
     16
     17See the **[source:/trunk/resources/data/defaultpresets.xml defaultpresets.xml]** for an example covering most of the possibilities listed below.
     18
     19Example:
     20
     21[[Image(Change 1 object.png,right,link=,margin-left=15)]]
    1422
    1523{{{
    16 #!xml
     24#!preset
     25<?xml version="1.0" encoding="UTF-8"?>
    1726<presets xmlns="http://josm.openstreetmap.de/tagging-preset-1.0">
    18   <item name="Highway">
    19     <label text="Inserting a highway in UK" />
    20 
    21     <text key="name" text="Highway (e.g. M3)" />
    22     <combo key="highway" text="Type" values="major,minor" />
    23 
    24     <!-- Highways are usually oneway -->
     27  <item name="Oneway highway" type="way">
     28    <label text="Inserting a unidirectional highway" />
     29
     30    <combo key="highway" text="Type" values="trunk,motorway" />
     31    <text key="name" text="Name (e.g. Angel Road)" />
     32    <text key="ref" text="Ref (e.g. A406)" />
     33
     34    <!-- This is a oneway preset, so make oneway default -->
    2535    <check key="oneway" text="Oneway" default="on" />
    2636
    27     <!-- Always setting class=highway -->
    28     <key key="class" value="highway" />
     37    <!-- Always setting asphalt surface -->
     38    <key key="surface" value="asphalt" />
    2939  </item>
    3040</presets>
    3141}}}
    32 
    33 
    34 == Develop a new preset – Add to the list of available presets ==
    35 
    36 See [[Presets]].
    37 
    38 
    39 == Develop a new preset – XML Format description ==
    40 
    41 The tagging preset description is in a very simple XML format.
    42 
    43 See the comment section in **[source:trunk/data/defaultpresets.xml defaultpresets.xml]** for the **valid format description**.
    44 
    45 ----
    46 
    47 == Develop a new preset – XML Format description (outdated!) ==
     42\\
     43
     44== XML Format description ==#XML
     45The full XSD schema is available at the namespace URI (https://josm.openstreetmap.de/tagging-preset-1.0) as well as [source:/trunk/resources/data/tagging-preset.xsd the source repository].
    4846
    4947=== Tags ===
    50 The document prolog:
    51  '''<presets>'''::
    52    Has to be the main tag of the file. Supports following attributes
    53    * '''xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"'''
    54    * '''author''' - the name of the author
    55    * '''version''' - a version of the file
    56    * '''description''' (i18n) - description what the file contains
    57    * '''shortdescription''' (i18n) - short overview description
    58    * '''link''' (i18n) - web link to further details
    59 Comments:
    60  '''<!-- this is an example comment -->'''::
    61   The document can contain embedded comments.
    62 Menu creation:
    63  '''<group>'''::
    64    Used to group items in sub menus. ''name'' is required, ''icon'' is optional attribute.
    65  '''<item>'''::
    66    Every item is one annotation set to select from. ''name'' is required, ''icon'' is optional attribute.
    67  '''<separator/>'''::
     48==== The document prologue ====
     49 <presets>::
     50  Has to be the main tag of the file. Supports following attributes
     51  * '''xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"'''
     52  * '''author''' - the name of the author of the preset
     53  * '''version''' - the version number of the file. For automatic version adjustment of presets managed in this wiki you have to use two internal variables: `[[revision]]` (the latest version number of the wiki page) and `[[date]]` (the date of the last edit), e.g. `version="1.[[revision]]_[[date]]"`.
     54  * '''description''' (i18n) - description what the file contains
     55  * '''shortdescription''' (i18n) - very short overview description i.e. the "name" of the preset
     56  * '''link''' (i18n) - web link to further details (optional)
     57  * '''icon''' - icon for the whole preset
     58  * '''baselanguage''' - when the base language is not English, specify it here (using non English preset texts will prevent automatic translation, once it is implemented (#11392))
     59
     60 (i18n) means the values may also be localized (e.g. `de.description`).
     61\\
     62
     63==== Comments ====
     64 <!-- this is an example comment -->::
     65   The document can contain embedded comments.
     66\\
     67
     68==== Preset group creation ====
     69 <group>::
     70   Used to group items in sub menus. `name=""` is required, `icon=""` is optional attribute.
     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.
     73 <separator />::
    6874   Insert a line separator into the menu.
    69 Create instructions for the user:
    70  '''<label>'''::
    71    Labels are static texts for display. ''text'' is a required attribute.
    72  '''<optional>'''::
    73    Used to group some optional elements of an item. Possibly equivalent to <label text="Optional Attributes:"/>
    74  '''<space/>'''::
    75    Add some space (ie a newline) in the preset display. Possibly equivalent to <label text=" "/>
    76  '''<link>'''::
    77    Specify a web link for this feature or to anything else of use. The ''href'' attribute is required.
    78 Attribute entry and selection dialog boxes:
    79  '''<text>'''::
    80    A text edit field to enter any arbitrary string from the user. ''key'' is mandatory, ''text'', ''default'' and ''required'' is optional
    81  '''<combo>'''::
    82    Displays a multiple choice combo box. ''key'' and ''values'' are mandatory and ''text'', ''default'', ''editable'' and ''required'' is optional.
    83    If editable is true (default), combo boxes can be edited as if they were text fields (additional to the drop down menu). Non editable
    84    combo boxes can only contain one of the specified values.
    85 
    86  '''<multiselect>'''::
    87    Displays a list from which zero or more items can be chosen. ''key'' and ''values'' are mandatory, and ''text'', ''default'', ''delimiter'', and ''required'' 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.
    88  '''<check>'''::
    89    A checkbox which the user can only select or deselect. The ''key'' attribute is mandatory. ''text'', ''default'' and ''required'' is optional.
    90 Set a key value pair:
    91  '''<key>'''::
    92    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 ommited, the key is removed.
     75\\
     76
     77==== Preset window layout ====
     78 <label />::
     79   Labels are static texts for display. `text=""` is a required attribute, `icon=""` and `icon_size=""` are optional.
     80 <space />::
     81   Add some space (i.e. a newline).
     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 />`
     84 <item_separator />::
     85   Add a horizontal separator line between items.
     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.
     88 <checkgroup>::
     89   To group checks. The `columns=""` attribute is required.
     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 />`.
     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.
     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.
     99\\
     100
     101==== Set a fixed key value pair ====
     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.
     104\\
     105
     106==== Attribute entry and selection dialog boxes ====#EntrySelectionBoxes
     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.
     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).
     113 [=#multiselect]
     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.
     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=""`.
     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.
     120\\
     121
     122==== Templates ====
     123 <chunk>::
     124   To define a template of elements for later (repeated) use. The `id=""` attribute is mandatory.
     125 <reference>::
     126   To include an earlier defined template. The `ref=""` attribute is mandatory.
     127\\
    93128
    94129=== Attributes ===
    95130The attributes of the tags have the following meaning:
    96  '''name="a_name"'''::
     131 name="a_name"::
    97132   Specify a name for an item. This name will be used in the GUI to display the tagging preset.
    98  '''name_context="context"'''::
     133 name_context="context"::
    99134   Translation context for name attribute to separate equals words with different meaning (not required for in-file translations).
    100  '''type="data_type"'''::
    101    When specified, only objects of the given type will be changed at all by this tagging preset. Can be "node", "relation", "way", "closedway" or any comma separated combination of them.
    102  '''icon="iconname"'''::
    103    A name of an icon that is within any classpath in the subdirectory of /images/symbols. You can load plugin-jar's to provide those images as well. The image will be used as icon to display in the selection list and when adding the preset to the toolbar. The icon should be quadratic in size.
    104  '''key="some_key"'''::
    105    This specifies the property key that will be modified by the item.
    106  '''text="Any text"'''::
    107    The description, that will be displayed before (after in case of <check>) the gui element.
    108  '''text_context="context"'''::
     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.
     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.
     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>`).
     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.
     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>`.
     145 text_context="context"::
    109146   Translation context for text attribute to separate equals words with different meaning (not required for in-file translations).
    110  '''default="default_value"'''::
    111    The default value for the item. If not specified, the current value of the key is chosen as default (if applicable).
    112  '''values="entry1,entry2,entry3"'''::
    113    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.
    114  '''values_context="context"'''::
    115    Translation context for name attribute to separate equals words with different meaning (not required for in-file translations).
    116  '''display_values="Entry1,Entry2,Entry3"'''::
    117    A list of entries that is displayed to the user. Must be the same number of entries as values and '''editable''' must be false or not specified. For the delimiter character and escaping, see the remarks at ''values''.
    118  '''value="foobar"'''::
    119    Specify a value to be entered in the <key> tag.
    120  '''value_on="foobar"'''::
    121    Specify the true value to be entered in the <key> tag (default is "yes").
    122  '''value_off="foobar"'''::
    123    Specify the false value to be entered in the <key> tag (default is "no").
    124  '''editable="false"'''::
    125    The combo box is readonly, which means that the user can only select an item in the list.
    126  '''use_last_as_default="true"'''::
    127    For combo boxes or text fields the last value is used as default. Using "force" enforces this behaviour also for already tagged objects.
    128  '''rows="count"'''::
    129    Specify the number of rows in multiselect entry.
    130 
    131 To support translations, all textual elements may be used in translated form. E.g. "de.name" would represent the name in case German language support is loaded.
    132 
    133 === Icon handling ===
    134 There are 3 different ways to source icons:
    135 
    136  * Icons distributed with JOSM can be entered directly with the path (relative to JOSM's internal image directory). Hunt through [http://josm.openstreetmap.de/svn/trunk/data/defaultpresets.xml this page] for the names of existing icons.
    137  * New icons can be directly referenced using a http-link. These are downloaded and cached internally.
    138  * Since JOSM version 2289 Zip-Files are supported.
    139   * The zip file must contain at least one file with extension xml.
    140   * Icon names and path are relative to the topmost zip directory.
    141   * If there are multiple XML files, a file with "preset" in the name is preferred (to allow packaging styles and presets in one archive).
     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''.
     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 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.
     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".
     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.
     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`.
     159 values_context="context"::
     160   Translation context for values attribute to separate equals words with different meaning (not required for in-file translations).
     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 />`.
     163 value="foobar"::
     164   Specify a value to be entered in the `<key>` tag.
     165 value_on="foobar"::
     166   Specify the true value to be entered in the `<key>` tag of a checked `<check />` (default is `"yes"`).
     167 value_off="foobar"::
     168   Specify the false value to be entered in the `<key>` tag of a unchecked `<check />` (default is `"no"`).
     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.
     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**.
     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"`.
     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.
     177 name_template="template", name_template_filter="search expression"::
     178   Custom name formatter for osm primitives matching this preset. See [#name_templatedetails name template details] below.
     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="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 id="unique_identifier"::
     191   the unique identifier for this `<chunk>`
     192 ref="unique_identifier"::
     193   the unique identifier of the (already defined) template to include
     194 columns="a number"::
     195   the number of columns of grouped `<check />`
     196 requisite="optional|required"::
     197   If a relation member is optional or required. Default is `"optional"`.
     198 count="a number"::
     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 regexp="true"::
     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`,...
     205 preset_name="exact_name"::
     206   The exact name of the preset to link to.
     207 preset_name_label="false|true"::
     208   Whether to insert "[preset name]" label in dialog (defaults to `"false"` for backward-compatibility on external presets).
     209 length="a number"::
     210   The length of a `<text />` or `<combo />` box (number of characters allowed).
     211 alternative_autocomplete_keys="some_key(s)"::
     212   A comma separated list of alternative keys to use for auto completion of `<text>`.
     213 auto_increment="-2,-1,+1,+2"::
     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=""`.
     215 delimiter="special character"::
     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].
     217 [=#short_description]
     218 short_descriptions="Entry1,Entry2,Entry3"::
     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="" />`
     221 values_searchable="true|false"::
     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 used, [#NameTemplateSyntax see below]. ''(since r17639)'' \\
     225   For instance, `"Bus {ref}: {from} → {to}"` can be used to generate the name of a bus route relation.
     226\\
     227
     228===== name_template details =====
     229Name templates can be used to define custom formatting for OSM primitives or GPX waypoints (for example in the Relations or the Selection).
     230
     231{{{
     232#!xml
     233<?xml version="1.0" encoding="UTF-8"?>
     234<presets>
     235        <item name="Public transportation" type="relation"
     236                name_template="Bus({operator} {ref} ?{'{from} - {via} - {to}' | '{from} - {to}' | '{from}' | '{to}'})"
     237                name_template_filter="type=route route=bus">
     238        </item>
     239</presets>
     240}}}
     241
     242'''Samples'''
     243||= Template =||= Tags =||= Result =||
     244|| `House number {addr:housenumber}` || `addr:housenumber=10` || House number 10
     245|| `?{ 'House number {addr:housenumber} at {addr:street}' | 'House number {addr:housenumber}'  }` || `addr:housenumber=10` || House number 10
     246|| || `addr:housenumber=10 addr:street=Abbey road` || House number 10 at Abbey road
     247|| `?{ admin_level = 2 'NUTS 1' | admin_level = 4 'NUTS 2' | admin_level = 6 'NUTS 3' |  'Admin level {admin_level}'}` ||  `admin_level=4` || NUTS 2
     248|| || `admin_level=5` || Admin level 5
     249|| `{admin_level} - {name} !{parent() type=boundary '?{'(part of {admin_level} - {name})' | ''}'}` || `admin_level=6 name=Vysocina`, member of relation `admin_level=4 name=Jihovychod` || 6 - Vysocina (part of Jihovychod)
     250|| ||  `admin_level=2 name=Czech republic` (no parents) || 2 - Czech republic
     251\\
     252
     253====== Syntax ======#NameTemplateSyntax
     254* `{var}` - use value of variable var
     255* `?{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
     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.
     257\\
     258
     259====== Available values ======
     260For formatting of OSM primitives , the value of any tag can be used. You can use `{special:everything}` to see what values are available for your gpx waypoints.
     261
     262Some additional variables are available  via the special prefix:
     263- `{special:everything}` prints all available values, available for formatting of both primitives and waypoints.
     264- `{special:id}` prints the ID of an osm primitive
     265- `{special:localName}` prints the localized name, that is the value of `name:lang` for your language if it is available or the value of the name tag if it doesn't.
     266\\
     267
     268=== Deprecated Attributes ===
     269The following attributes are deprecated and no longer supported by JOSM:
     270
     271 delete_if_empty="true"::
     272   was removed in r5155. You can simply remove this attribute if still used in your preset.
     273 required="true"::
     274   replaced by `match=""` since r5155
     275\\
     276
     277== Translation ==
     278To 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
     280In 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.
     281
     282The 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).
     283
     284The translation of external presets on this website is, so far, only possible inline within the preset source code, see #11392.
     285
     286== Icon handling ==
     287See [wikitr:/Styles#Iconhandling Styles].
    142288
    143289== See also ==
    144 * [/Presets]
    145 * [wiki:Help/Preferences/Map#TaggingPresets Tagging presets preferences]
     290* [wikitr:/Help/Menu/Presets Presets menu]