Changes between Version 188 and Version 198 of TaggingPresets

Timestamp:

(multiple changes)

Author:

(multiple changes)

Comment:

(multiple changes)

TaggingPresets

@@ -85 +85 @@
    Add a horizontal separator line between items.
  <link />::
-   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.
+   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. If using `wiki=""`, the OSM wiki page must not be URL encoded, e.g., it must not be `"Tag:leisure%3Dpark"` and must instead be `"Tag:leisure=park"`.
  <checkgroup>::
    To group checks. The `columns=""` attribute is required.
@@ -91 +91 @@
    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.
+   To specify possible roles of members in relations. The `key=""` attribute is required, `text=""`, `requisite=""`, `count=""`, `type=""`, `member_expression=""` and `regexp=""` are optional.
  <preset_link />::
    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. \\
@@ -170 +170 @@
    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 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**.
+   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 was not working properly for a long time but should work again since r18221, see #6157.)
  use_last_as_default="true|false|force"::
    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"`.
  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). Currently, you need to add one additional row to display all values, see #19013.
+   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 [#name_templatedetails name template details] below.
@@ -187 +187 @@
  match_expression="search expression"::
    additional criteria for matching primitives, specified in [wikitr:/Help/Action/Search JOSM search] syntax. ''(since r17662)'' \\
-   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. \\
-  **Note**: Does not work, yet, see #20843.
+   Quotes (`"`) need to be written as `&quot;`. \\
+   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.
  id="unique_identifier"::
    the unique identifier for this `<chunk>`
@@ -200 +200 @@
    How often can a role occur (if not given unlimited number is assumed)
  member_expression="search expression"::
-   an expression, in [wikitr:/Help/Action/Search JOSM search] syntax, for objects of this role
+   an expression, in [wikitr:/Help/Action/Search JOSM search] syntax, for objects of this role \\
+   Quotes (`"`) need to be written as `&quot;`.
  regexp="true"::
    set to `"true"` if the key of a role is a regular expression. \\
@@ -223 +224 @@
    Whether to search in `values=""` and `display_values=""`, respectively, `value=""` and `display_value=""` of `<combo />` or `<multiselect />` searching for presets.
  value_template="template"::
-   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)'' \\
+   A template to generate the value automatically based on other tag values of the object. The same syntax as in `name_template=""` is used, [#NameTemplateSyntax see below]. ''(since r17639)'' \\
    For instance, `"Bus {ref}: {from} → {to}"` can be used to generate the name of a bus route relation. \\
   **Note**: There are some minor problems with this attribute, see #20851 and #20861.
 \\
 
-===== name_template details ===== #name_templatedetails
-Name templates can be used to define custom formatting for OSM primitives or GPX waypoints (for example in the Relations or the Selection).
+===== name_template and value_template details ===== #name_templatedetails
+Name templates can be used to define custom formatting for OSM primitives or GPX waypoints (for example in the Relations or Selection panels).
 
 {{{
@@ -249 +250 @@
 || `?{ admin_level = 2 'NUTS 1' | admin_level = 4 'NUTS 2' | admin_level = 6 'NUTS 3' |  'Admin level {admin_level}'}` ||  `admin_level=4` || NUTS 2 
 || || `admin_level=5` || Admin level 5
-|| `{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} - {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 4 - Jihovychod)
 || ||  `admin_level=2 name=Czech republic` (no parents) || 2 - Czech republic
 \\
 
 ====== Syntax ======#NameTemplateSyntax
-* `{var}` - use value of variable var
-* `?{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
+* `{tag}` - insert the value of the tag.
+* `?{condition1 'value1' | condition2 'value2' | 'value3'}` - use ''value1'' if ''condition1'' is satisfied, else use ''value2'' if ''condition2'' is satisfied, finally use ''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 tags referenced 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.
+* `\` - use a backslash to escape special characters '{', '}', '?', '!'.  E.g. `What is this\? It is a {type}\!`.
 \\
 
 ====== Available values ======
-For 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.
-
-Some additional variables are available  via the special prefix:
+For formatting of OSM primitives, the value of any tag can be used. Use the tag `{special:everything}` to display all available tags, eg. on your gpx waypoints.
+
+You can also use these virtual tags:
 - `{special:everything}` prints all available values, available for formatting of both primitives and waypoints.
-- `{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.
+- `{special:id}` prints the ID of the 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 `name` if it is not.
 \\
 
@@ -278 +280 @@
 
 == 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. 
-
-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).
-
-The translation of external presets on this website is, so far, only possible inline within the preset source code, see #11392.
+To support translations, all textual elements (`name=""`, `text=""`, `display_values=""`) can be localized. E.g. `de.name=""` would represent the name when the German language support is loaded. In the preset XML code the English term must be the first, before possible translations can be added.
+
+=== Internal Preset ===
+The translation for the internal preset is done at [https://translations.launchpad.net/josm/trunk Launchpad].
+
+In the [source:josm/trunk/resources/data/defaultpresets.xml internal preset], all `name=""`, `text=""` and `display_values=""` are translated via the above service, as long as no specific translation has been given within XML file. When no `display_values=""` are supplied, then `values=""` will be treated as `display_values=""` and translated instead. 
+
+When the same English word has different translations in different contexts, the specific translation context needs to be specified. Use `name_context=""`, `text_context=""` or `values_context=""` for this purpose. The context should be a meaningful short description to help translators. 
+
+=== External Presets ===
+
+The translation of external presets on this website is, so far, only possible inline within the preset XML source code, see #11392.
+
+Presets hosted elsewhere can also add a `data` directory with the JOSM-style {{{.lang}}} files for translation (like in JOSM itself or plugins).
+
+However, when words are used in the external preset that already exist in the internal preset, the translation from the internal preset applies to the external as well. This is useful as long as the context is the same. When the context in the external preset is different, it needs to be distinguished by adding `name_context=""`, `text_context=""` or `values_context=""`.
 
 == Icon handling ==