Changes between Version 151 and Version 152 of TaggingPresets

Timestamp:

2020-03-06T21:11:55+01:00 (6 years ago)

Author:

Klumbumbus

Comment:

link fix /resources

TaggingPresets

@@ -247 +247 @@
 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/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. 
+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).