Changes between Version 152 and Version 153 of TaggingPresets

Timestamp:

2020-03-19T17:46:20+01:00 (6 years ago)

Author:

skyper

Comment:

use same format on whole page; wikitr:

TaggingPresets

@@ -1 @@
-''If you want to learn installation steps for presets, see [Help/Preferences/Map#TaggingPresets "Tagging Presets" tab in Preferences > Map Settings]''[[br]]
-''If you want to use presets or need complete reference of presets see [wiki:Presets Presets]''[[br]]
+''If you want to learn installation steps for presets, see [wikitr:/Help/Preferences/Map#TaggingPresets "Tagging Presets" tab in Preferences > Map Settings]''\\
+''If you want to use presets or need complete reference of presets see [wikitr:/Presets Presets]''\\
+
 [[TranslatedPages]]
 [[PageOutline(2-10,Table of Contents)]]
+
 = Tagging Presets =
 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). 
@@ -11 +13 @@
 The tagging preset description is in a very simple XML format. Details see [#XML below].
 
-See the **[source:trunk/resources/data/defaultpresets.xml defaultpresets.xml]** for an example covering most of the possibilities listed below.
+See the **[source:/trunk/resources/data/defaultpresets.xml defaultpresets.xml]** for an example covering most of the possibilities listed below.
 
 Example:
@@ -35 +37 @@
 </presets>
 }}}
+\\
 
 == XML Format description ==#XML
-
-The full XSD schema is available at the namespace URI (http://josm.openstreetmap.de/tagging-preset-1.0) as well as [source:trunk/resources/data/tagging-preset.xsd the source repository].
+The 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].
+
 === Tags ===
 ==== The document prolog ====
@@ -49 +52 @@
   * '''shortdescription''' (i18n) - very short overview description i.e. the "name" of the preset
   * '''link''' (i18n) - web link to further details (optional)
-  * '''icon''' - informational icon for the whole preset. (This is nedded to display the icon in the table at [[Presets]].)
+  * '''icon''' - informational icon for the whole preset. (This is nedded to display the icon in the table at [wikitr:/Presets Presets].)
   * '''baselanguage''' - when the base language is not English, specify it here (using non English preset texts prevents automatic translation)
 
   (i18n) means the values may also be localized (e.g. de.description).
-[[BR]]
+\\
+
 ==== Comments ====
  <!-- this is an example comment -->::
   The document can contain embedded comments.
-[[BR]]
+\\
+
 ==== Preset group creation ====
  <group>::
@@ -65 +70 @@
  <separator/>::
   Insert a line separator into the menu.
-[[BR]]
+\\
+
 ==== Preset window layout ====
  <label>::
@@ -72 +78 @@
   Add some space (ie a newline).
  <optional>::
-  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 />
+  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 />`
  <item_separator />::
   Add a horizontal separator line between items.
@@ -80 +86 @@
   To group checks. The `columns` attribute is required.
  <roles>::
-  This is required around <role> and adds the heading ("Availible roles role count elements") to the table which is generated by several <role>.
+  This is required around `<role>` and adds the heading ("Available roles role count elements") to the table which is generated by several `<role>`.
  <role>::
   To specify possible roles of members in relations. The `key` attribute is required, `text`, `requisite`, `count`, `type` and `member_expression` are optional.
  <preset_link>::
   Adds a link to an other preset. The `preset_name` attribute is required.
-[[BR]]
+\\
+
 ==== Set a fixed key value pair ====
  <key>::
-  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. The `match` attribute is optional.
-[[BR]]
+  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.
+\\
+
 ==== Attribute entry and selection dialog boxes ====
  <text>::
@@ -95 +103 @@
  <combo>::
   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` and `match` is optional.\\
-  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.
- <multiselect>::
-  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` and `match` 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.
+  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.
+ <multiselect>:: [=#multiselect]
+  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` and `match` 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.
  <list_entry>::
   Used in <combo> and <multiselect>. More information see `short_descriptions`. The attributes are `value`, `display_value`, `short_description`, `icon` and `icon_size`.
  <check>::
   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.
-[[BR]]
+\\
+
 ==== Templates ====
  <chunk>::
@@ -108 +117 @@
  <reference>::
   To include an earlier defined template. The `ref` attribute is mandatory.
-[[BR]]
+\\
+
 === Attributes ===
 The attributes of the tags have the following meaning:
@@ -116 +126 @@
   Translation context for name attribute to separate equals words with different meaning (not required for in-file translations).
  type="data_type"::
-  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.
+  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.
  icon="iconname"::
-  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> and <list_entry>. The icon should be quadratic in size. See [[Styles#Iconhandling]] how icons can be specified.
+  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>` and `<list_entry>`. The icon should be quadratic in size. See [wikitr:/Styles#Iconhandling Icon handling] how icons can be specified.
  icon_size="a number"::
-  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>).
+  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>`).
  key="some_key"::
-  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.
+  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.
  text="Any text"::
-  The description, that will be displayed before (after in case of <check>) the gui element. Also used for <label> and <optional>.
+  The description, that will be displayed before (after in case of `<check>`) the gui element. Also used for `<label>` and `<optional>`.
  text_context="context"::
   Translation context for text attribute to separate equals words with different meaning (not required for in-file translations).
  default="default_value"::
   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''.
-  If no value for default is specified, no value is set to the key. Used in <check>, <text>, <combo> and <multiselect>.
+  If no value for default is specified, no value is set to the key. Used in `<check>`, `<text>`, `<combo>` and `<multiselect>`.
  values="entry1,entry2,entry3"::
-  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.
+  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.
  values_from="JAVA code"::
-  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".
+  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.)
+  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"::
-  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 globaly disable sorting with the preference key `taggingpreset.sortvalues`.
+  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`.
  values_context="context"::
   Translation context for values attribute to separate equals words with different meaning (not required for in-file translations).
  display_values="Entry1,Entry2,Entry3"::
-  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>.
+  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>`.
  value="foobar"::
-  Specify a value to be entered in the <key> tag.
+  Specify a value to be entered in the `<key>` tag.
  value_on="foobar"::
-  Specify the true value to be entered in the <key> tag of a checked <check> (default is "yes").
+  Specify the true value to be entered in the `<key>` tag of a checked `<check>` (default is `"yes"`).
  value_off="foobar"::
-  Specify the false value to be entered in the <key> tag of a unchecked <check> (default is "no").
+  Specify the false value to be entered in the `<key>` tag of a unchecked `<check>` (default is `"no"`).
  disable_off="true"::
-  Whether the off value of a <check> is disabled in the dialog, i.e., only unset or yes are provided.
+  Whether the off value of a `<check>` is disabled in the dialog, i.e., only unset or `"yes"` are provided.
  editable="false"::
-  The combo box is readonly, 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.
+  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.
  use_last_as_default="true|false|force"::
-  For <combo>, <multiselect> or <text> fields the last value is used as default. Using "force" enforces this behaviour also for already tagged objects. Default is "false".
+  For `<combo>`, `<multiselect>` or `<text>` fields the last value is used as default. Using `"force"` enforces this behaviour also for already tagged objects. Default is `"false"`.
  rows="count"::
-  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).
+  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).
  name_template="template", name_template_filter="search expression"::
   Custom name formatter for osm primitives matching this preset. See below [[#name_templatedetails]] for details.
  match="none|key|key!|keyvalue|keyvalue!"::
-  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 [wiki:Help/Dialog/TagsMembership Tags/Membership dialog].
-  * none: neutral, i.e., do not consider this item for matching
-  * key: positive if key matches, neutral otherwise
-  * key!: positive if key matches, negative otherwise
-  * keyvalue: positive if key and value matches, neutral otherwise
-  * keyvalue!: positive if key and value matches, negative otherwise
-
-  Note that 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>.
+  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].
+  * `none`: neutral, i.e., do not consider this item for matching
+  * `key`: positive if key matches, neutral otherwise
+  * `key!`: positive if key matches, negative otherwise
+  * `keyvalue`: positive if key and value matches, neutral otherwise
+  * `keyvalue!`: positive if key and value matches, negative otherwise
+
+  Note that 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>`.
  id="unique_identifier"::
-  the unique identifier for this chunk
+  the unique identifier for this `<chunk>`
  ref="unique_identifier"::
   the unique identifier of the (already defined) template to include
  columns="a number"::
-  the number of columns of grouped checks
+  the number of columns of grouped `<check>`
  requisite="optional|required"::
-  If a relation member is optional or required. Default is "optional".
+  If a relation member is optional or required. Default is `"optional"`.
  count="a number"::
   How often can a role occur (if not given unlimited number is assumed)
@@ -180 +191 @@
   an expression (cf. search dialog) for objects of this role
  regexp="true"::
-  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,...
+  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,...
  preset_name="exact_name"::
   The exact name of the preset to link to.
  preset_name_label="false|true"::
-  Whether to insert "[preset name]" label in dialog (defaults to "false" for backward-compatibility on external presets).
+  Whether to insert "[preset name]" label in dialog (defaults to `"false"` for backward-compatibility on external presets).
  length="a number"::
-  The length of a <text> or <combo> box (number of characters allowed).
+  The length of a `<text>` or `<combo>` box (number of characters allowed).
  alternative_autocomplete_keys="some_key(s)"::
-  A comma separated list of alternative keys to use for autocompletion of <text>.
+  A comma separated list of alternative keys to use for auto completion of `<text>`.
  auto_increment="-2,-1,+1,+2"::
-  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`.
+  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`.
  delimiter="special character"::
-  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>.
- short_descriptions=""Entry1,Entry2,Entry3"::
-  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 comma separated list instead using values, display_values and short_descriptions, the following form is also supported: <list_entry value="" display_value="" short_description="" icon="" icon_size="" />
+  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].
+ short_descriptions="Entry1,Entry2,Entry3"::
+  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 comma separated list instead using `values`, `display_values` and `short_descriptions`, the following form is also supported: `<list_entry value="" display_value="" short_description="" icon="" icon_size="" />`
  values_searchable="true|false"::
-  Whether to search in <combo> or <multiselect> (display_)values when searching for presets.
+  Whether to search in `<combo>` or `<multiselect>` (display_)values when searching for presets.
+\\
 
 ===== name_template details =====
-
-**Name templates can be used to define custom formatting for OSM primitives or GPX waypoints** (for example in the Relations or the Selection).
+Name templates can be used to define custom formatting for OSM primitives or GPX waypoints (for example in the Relations or the Selection).
 
 {{{
@@ -222 +233 @@
 || `{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)
 || ||  `admin_level=2 name=Czech republic` (no parents) || 2 - Czech republic
+\\
 
 ====== Syntax ======
@@ -227 +239 @@
 * `?{condition1 'value1' | condition2 'value2 | 'value3'}` - use value1 if condition1 is satisfied, value3 is no 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 exist
 * `!{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.
+\\
 
 ====== Available values ======
@@ -235 +248 @@
 - `{special:id}` prints the ID of an osm primitive
 - `{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.
+\\
 
 === Deprecated Attributes ===
@@ -243 +257 @@
  required="true"::
   replaced by `match` since [5155]
+\\
 
 == Translation ==
-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.
-
-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. 
+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.
+
+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. 
 
 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).
 
 == Icon handling ==
-See [wiki:Styles#Iconhandling Styles].
+See [wikitr:/Styles#Iconhandling Styles].
 
 == See also ==
-* [wiki:Help/Menu/Presets Presets menu]
+* [wikitr:/Help/Menu/Presets Presets menu]