Changes between Initial Version and Version 1 of Nl:TaggingPresets


Ignore:
Timestamp:
2016-02-11T19:24:32+01:00 (10 years ago)
Author:
DiGro
Comment:

translating into Dutch

Legend:

Unmodified
Added
Removed
Modified
  • Nl:TaggingPresets

    v1 v1  
     1[[TranslatedPages(revision=126)]]
     2[[PageOutline(2-10,Inhoud)]]
     3= Voorkeuzen voor tags =
     4JOSM ondersteund gedeelde voorkeuzen voor tags. Dit is een XML configuratiebestand dat een GUI beschrijft voor het invoeren van tags (of eigenschappen, opmerkingen, soms ook wel kaartobjecten genoemd). De XML-bestanden kunnen overal op het web geplaatst worden of op het lokale bestandssysteem van de gebruiker. Voorkeuzen kunnen door gebruikers worden toegevoegd op een centrale plaats pagina [wiki:Presets].
     5
     6== Installeren van voorkeuzen ==
     7Ofwel:
     8* Klik in het hoofdmenu op [wiki:/Nl:Help/Menu/Presets Voorkeuzen] en klik op "Voorkeuren voor voorkeuzen".
     9* Open het [wiki:/Nl:Help/Action/Preferences venster voor de voorkeuren], klik op [[Image(source:trunk/images/preferences/map.png,20)]] kaartinstellingen en selecteer de derde tab [wiki:/Nl:Help/Preferences/Map#Voorafingesteldetags "Vooraf ingestelde tags"].
     10
     11== Een nieuwe voorkeuze ontwikkelen ==
     12De beschrijving van een voorkeuze voor taggen staat in een zeer eenvoudige XML-indeling. Voor details zie [#XML hieornder].
     13
     14Bekijk **[source:trunk/data/defaultpresets.xml defaultpresets.xml]** voor een voorbeeld dat de meeste mogelijkhedne behandelt van die welke hieronder vermeld zijn.
     15
     16Het volledige XSD-schema is beschikbaar op de namespace URI (http://josm.openstreetmap.de/tagging-preset-1.0) en ook in [source:trunk/data/tagging-preset.xsd de bron repository].
     17
     18Bekijk [[Presets#Createnewpresets]] om de voorkeuze toe te voegen aan de lijst met beschikbare voorkeuzen.
     19
     20Voorbeeld:
     21[[Image(Change 1 object.png,align=right)]]
     22
     23{{{
     24#!xml
     25<presets xmlns="http://josm.openstreetmap.de/tagging-preset-1.0">
     26  <item name="Oneway highway" type="way">
     27    <label text="Invoegen van een één richting highway" />
     28
     29    <combo key="highway" text="Type" values="trunk,motorway" />
     30    <text key="name" text="Name (bijv. Angel Road)" />
     31    <text key="ref" text="Ref (bijv. A406)" />
     32
     33    <!-- Dit is een voorkeuze voor één richting dus maak oneway de standaard -->
     34    <check key="oneway" text="Oneway" default="on" />
     35
     36    <!-- Altijd het oppervlak asphalt instellen -->
     37    <key key="surface" value="asphalt" />
     38  </item>
     39</presets>
     40}}}
     41
     42Het gereedschap [http://visualtags.hotosm.org/ HOT Visual Tag Chooser] stelt de gebruiker in staat een Tagging Preset File te maken of te bewerken door middel van een webinterface.
     43
     44== Beschrijving XML-indeling ==#XML
     45=== Tags ===
     46==== De proloog van het document ====
     47 <presets>::
     48  Moet de hoofdtag van het bestand zijn. Ondersteund de volgende attributen
     49  * '''xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"'''
     50  * '''author''' - de naam van de auteur van de voorkeuze
     51  * '''version''' - het versienummer van het bestand. Voor geautomatiseerde versie-aanpassingen van de voorkeuzen die worden beheerd op deze wiki kunt u twee interne variabelen gebruiken: `[[revision]]` (het laatste versienummer van de pagina op de wiki) en `[[date]]` (de datum van de laatste bewerking).
     52  * '''description''' (i18n) - beschrijving van wat het bestand bevat
     53  * '''shortdescription''' (i18n) - zeer korte overzichtsbeschrijving d.i. de "naam" van de voorkeuze
     54  * '''link''' (i18n) - weblink voor meer details (optioneel)
     55  * '''icon''' - informatief pictogram voor de gehele voorkeuze. (Dit is nodig om het pictogram weer te geven in de tabel van [[Presets]].)
     56  * '''baselanguage''' - wanneer de basistaal niet Engels is, specificeer die dan hier (gebruiken van niet-Engelse teksten voor voorkeuze voorkomt automatisch vertalen)
     57
     58  (i18n) betekent dat de waarden ook mogen zijn gelokaliseerd (bijv. de.description).
     59[[BR]]
     60==== Opmerkingen ====
     61 <!-- dit is een voorbeeld opmerking -->::
     62  Het document mag ingebedde opmerkingen bevatten.
     63[[BR]]
     64==== Maken van een menu ====
     65 <group>::
     66  Gebruikt om items te groeperen in submenu's. `name` is vereist, `icon` is een optioneel attribuut.
     67 <item>::
     68  Elk item is één ingestelde opmerking om uit te selecteren. `name` is vereist, `type` en `preset_name_label` worden aanbevolen, `icon` en `name_template` zijn optionele attributen.
     69 <separator/>::
     70  Voegt een scheidingslijn in het menu in.
     71[[BR]]
     72==== Preset window layout ====
     73 <label>::
     74  Labels are static texts for display. `text` is a required attribute, `icon` and `icon_size` are optional.
     75 <space />::
     76  Add some space (ie a newline).
     77 <optional>::
     78  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 />
     79 <item_separator />::
     80  Add a horizontal separator line between items.
     81 <link>::
     82  Specify a web link for this feature or to anything else of use. The `href` attribute is required.
     83 <checkgroup>::
     84  To group checks. The `columns` attribute is required.
     85 <roles>::
     86  This is required around <role> and adds the heading ("Availible roles role count elements") to the table which is generated by several <role>.
     87 <role>::
     88  To specify possible roles of members in relations. The `key` attribute is required, `text`, `requisite`, `count`, `type` and `member_expression` are optional.
     89 <preset_link>::
     90  Adds a link to an other preset. The `preset_name` attribute is required.
     91[[BR]]
     92==== Set a fixed key value pair ====
     93 <key>::
     94  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.
     95[[BR]]
     96==== Attribute entry and selection dialog boxes ====
     97 <text>::
     98  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` and `match` is optional
     99 <combo>::
     100  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.\\
     101  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.
     102 <multiselect>::
     103  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.
     104 <list_entry>::
     105  Used in <combo> and <multiselect>. More information see `short_descriptions`. The attributes are `value`, `display_value`, `short_description`, `icon` and `icon_size`.
     106 <check>::
     107  A checkbox which the user can only select or deselect (or set as unset). The `key` attribute is mandatory. `text`, `default`, `match`, `value_on` , `value_off` and `disable_off` are optional.
     108[[BR]]
     109==== Templates ====
     110 <chunk>::
     111  To define a template of elements for later (repeated) use. The `id` attribute is mandatory.
     112 <reference>::
     113  To include an earlier defined template. The `ref` attribute is mandatory.
     114[[BR]]
     115=== Attributes ===
     116The attributes of the tags have the following meaning:
     117 name="a_name"::
     118  Specify a name for an item. This name will be used in the GUI to display the tagging preset.
     119 name_context="context"::
     120  Translation context for name attribute to separate equals words with different meaning (not required for in-file translations).
     121 type="data_type"::
     122  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.
     123 icon="iconname"::
     124  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.
     125 icon_size="a number"::
     126  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>).
     127 key="some_key"::
     128  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.
     129 text="Any text"::
     130  The description, that will be displayed before (after in case of <check>) the gui element. Also used for <label> and <optional>.
     131 text_context="context"::
     132  Translation context for text attribute to separate equals words with different meaning (not required for in-file translations).
     133 default="default_value"::
     134  The default value for the item. If not specified, the current value of the key is chosen as default (if applicable). In case of <check> whether the checkbox is ticked on or off by default (default is "off"). In case of <text>, <combo> and <multiselct> defaults to "".
     135 values="entry1,entry2,entry3"::
     136  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.
     137 values_from="JAVA code"::
     138  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".
     139 values_no_i18n="true|false"::
     140  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.)
     141 values_sort="false"::
     142  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 for the keys "smoothness" and "trail_visibility".) Default is "true". Users can globaly disable sorting with the preference key `taggingpreset.sortvalues`.
     143 values_context="context"::
     144  Translation context for values attribute to separate equals words with different meaning (not required for in-file translations).
     145 display_values="Entry1,Entry2,Entry3"::
     146  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>.
     147 value="foobar"::
     148  Specify a value to be entered in the <key> tag.
     149 value_on="foobar"::
     150  Specify the true value to be entered in the <key> tag of a checked <check> (default is "yes").
     151 value_off="foobar"::
     152  Specify the false value to be entered in the <key> tag of a unchecked <check> (default is "no").
     153 disable_off="true"::
     154  Whether the off value of a <check> is disabled in the dialog, i.e., only unset or yes are provided.
     155 editable="false"::
     156  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.
     157 use_last_as_default="true|false|force"::
     158  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".
     159 rows="count"::
     160  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).
     161 name_template="template", name_template_filter="search expression"::
     162  Custom name formatter for osm primitives matching this preset. See [[NameTemplate]] for details.
     163 match="none|key|key!|keyvalue|keyvalue!"::
     164  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].
     165  * none: neutral, i.e., do not consider this item for matching
     166  * key: positive if key matches, neutral otherwise
     167  * key!: positive if key matches, negative otherwise
     168  * keyvalue: positive if key and value matches, neutral otherwise
     169  * keyvalue!: positive if key and value matches, negative otherwise
     170
     171  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>.
     172 id="unique_identifier"::
     173  the unique identifier for this chunk
     174 ref="unique_identifier"::
     175  the unique identifier of the (already defined) template to include
     176 columns="a number"::
     177  the number of columns of grouped checks
     178 requisite="optional|required"::
     179  If a relation member is optional or required. Default is "optional".
     180 count="a number"::
     181  How often can a role occur (if not given unlimited number is assumed)
     182 member_expression="an expression"::
     183  an expression (cf. search dialog) for objects of this role
     184 preset_name="exact_name"::
     185  The exact name of the preset to link to.
     186 preset_name_label="false|true"::
     187  Whether to insert "[preset name]" label in dialog (defaults to "false" for backward-compatibility on external presets).
     188 length="a number"::
     189  The length of a <text> or <combo> box (number of characters allowed).
     190 alternative_autocomplete_keys="some_key(s)"::
     191  A comma separated list of alternative keys to use for autocompletion of <text>.
     192 auto_increment="-2,-1,+1,+2"::
     193  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`.
     194 delimiter="special character"::
     195  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>.
     196 short_descriptions=""Entry1,Entry2,Entry3"::
     197  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="" />
     198 values_searchable="true|false"::
     199  Whether to search in <combo> or <multiselect> (display_)values when searching for presets.
     200
     201=== Deprecated Attributes ===
     202The following attributes are deprecated and no longer supported by JOSM:
     203
     204 delete_if_empty="true"::
     205  was removed in [5155]. You can simply remove this attribute if still used in your preset.
     206 required="true"::
     207  replaced by `match` since [5155]
     208
     209== Translation ==
     210To support translations, all textual elements ("name", "text", "display_values") may also be localized. (E.g. "de.name" would represent the name in case German language support is loaded.)
     211
     212In JOSM internally ([source:josm/trunk/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).
     213
     214== Icon handling ==
     215See [wiki:Styles#Iconhandling Styles].
     216
     217== See also ==
     218* [wiki:Presets]
     219* [wiki:Help/Menu/Presets Presets menu]
     220* [wiki:Help/Preferences/Map#TaggingPresets Tagging presets preferences]