Changes between Initial Version and Version 5 of Ticket #24014
- Timestamp:
- 2024-11-20T12:32:59+01:00 (14 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24014
- Property Milestone → 24.11
- Property Cc added
-
Ticket #24014 – Description
initial v5 1 I was adding `operator:wikidata` tags to some nodes (e.g. https://www.openstreetmap.org/node/12344145506). These nodes have an `inscription=` tag created by iD that's using `\n` in its value to signify line breaks. According to https://wiki.openstreetmap.org/wiki/Key:inscription, this is a valid usage. 1 I was adding `operator:wikidata` tags to some nodes (e.g. https://www.openstreetmap.org/node/12344145506). These nodes have an `inscription=` tag created by iD that's using `\n` (literal newline characters, `U+000A`, displayed as `\n` if you're using the textbox tag editor), in its value to signify line breaks. According to https://wiki.openstreetmap.org/wiki/Key:inscription, this is a valid usage. 2 2 3 However, after uploading the changes via JOSM (changeset https://www.openstreetmap.org/changeset/159245848), the inscriptions all lost their `\n` linebreaks. I'm not exactly sure whether JOSM converted them to actual newline characters (instead of a backslash followed by an `n`) or replaced them with spaces. In any case, it should not do that, especially not in a totally silent way when my edit didn't even change the tag value at all. I'm glad that I saw this happening and was able to revert it; pretty sure that not everyone would.3 However, after uploading the changes via JOSM (changeset https://www.openstreetmap.org/changeset/159245848), the inscriptions all lost their `\n` linebreaks. JOSM seems to have replaced them with spaces. It should not do that, especially not in a totally silent way when my edit didn't even change the tag value at all. I'm glad that I saw this happening and was able to revert it; pretty sure that not everyone would. 4 4 5 5 Adding the status report manually because the "Report bug" button would send me to Debian's bug tracker, but I don't assume this is Debian-specific behavior. Let me know if you need more information, and thanks for looking into this.


