Attachments (2)
Change History (9)
by , 14 years ago
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:2 by , 14 years ago
"No" has to different etymology in english : the first means "none" ("aucun" in french, "kein" in german).
http://en.wiktionary.org/wiki/no#Etymology_1
The second is the opposite of "Yes" ("Non" in french, "Nein" in german).
http://en.wiktionary.org/wiki/no#Etymology_2
Sometimes when "No" is used as a value in JOSM, the translation uses the wrong etymology.
comment:3 by , 14 years ago
A said. In this case we must either add display_values, which has an entry for each entry in values. Or we simply add a values_context, which allows to translate it individual.
comment:4 by , 14 years ago
| Summary: | [Patch] Improve translation → [Patch needs rework] Improve translation |
|---|
by , 14 years ago
| Attachment: | 6588v2.patch added |
|---|
comment:5 by , 14 years ago
| Summary: | [Patch needs rework] Improve translation → [Patch] Improve translation |
|---|
Patch attached.
Just to consider: displaying "Recording: no" (instead of "none") is all right?
comment:7 by , 14 years ago
Patch not used: Rather than confusing users I added properly I18n marker.
Nevertheless thanks for this patch and all the others :-)
I don't think so. "none" is no standard value in OSM database. We always use "no". We could add "display_values", but we can't change "values".
P.S. Please name your patches with extension".diff" or ".patch". "patch.txt" is no good name, as it prevents syntax highlighting.