CalvinBackup/iD
1
0
Fork 0
mirror of https://github.com/FoggedLens/iD.git synced 2026-05-16 13:59:27 +02:00
Code Issues Packages Projects Releases Wiki Activity

Periods in non-sentence message headings look strange

Browse Source
This commit is contained in:
Bryan Housel
2019-02-11 13:30:28 -05:00
parent b34dceeeb1
commit ac23ac8fd2
2 changed files with 41 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
data/core.yaml
+31 -31
View File
@@ -1177,69 +1177,69 @@ en:
message: Everything looks fine.
info: Any issues will show up here as you edit.
almost_junction:
message: "{feature} is very close but not connected to {feature2}."
message: "{feature} is very close but not connected to {feature2}"
highway-highway:
tip: Intersecting highways should share a junction vertex.
crossing_ways:
message: "{feature} crosses {feature2}."
message: "{feature} crosses {feature2}"
building-building:
tip: Buildings should not intersect except on different layers.
tip: "Buildings should not intersect except on different layers."
building-highway:
tip: Highways crossing buildings should use bridges, tunnels, coverings, or entrances.
tip: "Highways crossing buildings should use bridges, tunnels, coverings, or entrances."
building-railway:
tip: Railways crossing buildings should use bridges or tunnels.
tip: "Railways crossing buildings should use bridges or tunnels."
building-waterway:
tip: Waterways crossing buildings should use tunnels or different layers.
tip: "Waterways crossing buildings should use tunnels or different layers."
highway-highway:
tip: Crossing highways should use bridges, tunnels, or intersections.
tip: "Crossing highways should use bridges, tunnels, or intersections."
highway-railway:
tip: Highways crossing railways should use bridges, tunnels, or level crossings.
tip: "Highways crossing railways should use bridges, tunnels, or level crossings."
highway-waterway:
tip: Highways crossing waterways should use bridges, tunnels, or fords.
tip: "Highways crossing waterways should use bridges, tunnels, or fords."
railway-railway:
tip: Crossing railways should be connected or use bridges or tunnels.
tip: "Crossing railways should be connected or use bridges or tunnels."
railway-waterway:
tip: Railways crossing waterways should use bridges or tunnels.
tip: "Railways crossing waterways should use bridges or tunnels."
waterway-waterway:
tip: Crossing waterways should be connected or use tunnels.
tip: "Crossing waterways should be connected or use tunnels."
tunnel-tunnel:
tip: Crossing tunnels should use different layers.
tip: "Crossing tunnels should use different layers."
tunnel-tunnel_connectable:
tip: Crossing tunnels should be connected or use different layers.
tip: "Crossing tunnels should be connected or use different layers."
bridge-bridge:
tip: Crossing bridges should use different layers.
tip: "Crossing bridges should use different layers."
bridge-bridge_connectable:
tip: Crossing bridges should be connected or use different layers.
tip: "Crossing bridges should be connected or use different layers."
deprecated_tag:
message: '{feature} has outdated tags: {tags}'
tip: Some tags become deprecated over time and should be replaced.
tip: "Some tags become deprecated over time and should be replaced."
disconnected_way:
highway:
message: "{highway} is disconnected from other roads and paths."
tip: Highways should connect to other highways or building entrances.
message: "{highway} is disconnected from other roads and paths"
tip: "Highways should connect to other highways or building entrances."
generic_name:
message: '{feature} has the generic name "{name}".'
tip: Names should be the official, on-the-ground titles of features.
message: '{feature} has the generic name "{name}"'
tip: "Names should be the official, on-the-ground titles of features."
many_deletions:
points-lines-areas:
message: "Deleting {n} features: {p} points, {l} lines, and {a} areas."
message: "Deleting {n} features: {p} points, {l} lines, and {a} areas"
points-lines-areas-relations:
message: "Deleting {n} features: {p} points, {l} lines, {a} areas, and {r} relations."
tip: Only redundant or nonexistent features should be deleted.
message: "Deleting {n} features: {p} points, {l} lines, {a} areas, and {r} relations"
tip: "Only redundant or nonexistent features should be deleted."
missing_tag:
any:
message: "{feature} has no tags."
message: "{feature} has no tags"
descriptive:
message: "{feature} has no descriptive tags."
message: "{feature} has no descriptive tags"
specific:
message: '{feature} has no "{tag}" tag.'
tip: Features must have tags that define what they are.
message: '{feature} has no "{tag}" tag'
tip: "Features must have tags that define what they are."
old_multipolygon:
message: "{multipolygon} has misplaced tags."
tip: Multipolygons should be tagged on their relation, not their outer way.
message: "{multipolygon} has misplaced tags"
tip: "Multipolygons should be tagged on their relation, not their outer way."
tag_suggests_area:
message: "{feature} should be a closed area based on the tag: {tag}"
tip: Areas must have connected endpoints.
tip: "Areas must have connected endpoints."
fix:
add_connection_vertex:
title: Connect the features
dist/locales/en.json
Vendored
+10 -10
View File
@@ -1427,13 +1427,13 @@
"info": "Any issues will show up here as you edit."
},
"almost_junction": {
"message": "{feature} is very close but not connected to {feature2}.",
"message": "{feature} is very close but not connected to {feature2}",
"highway-highway": {
"tip": "Intersecting highways should share a junction vertex."
}
},
"crossing_ways": {
"message": "{feature} crosses {feature2}.",
"message": "{feature} crosses {feature2}",
"building-building": {
"tip": "Buildings should not intersect except on different layers."
},
@@ -1483,37 +1483,37 @@
},
"disconnected_way": {
"highway": {
"message": "{highway} is disconnected from other roads and paths.",
"message": "{highway} is disconnected from other roads and paths",
"tip": "Highways should connect to other highways or building entrances."
}
},
"generic_name": {
"message": "{feature} has the generic name \"{name}\".",
"message": "{feature} has the generic name \"{name}\"",
"tip": "Names should be the official, on-the-ground titles of features."
},
"many_deletions": {
"points-lines-areas": {
"message": "Deleting {n} features: {p} points, {l} lines, and {a} areas."
"message": "Deleting {n} features: {p} points, {l} lines, and {a} areas"
},
"points-lines-areas-relations": {
"message": "Deleting {n} features: {p} points, {l} lines, {a} areas, and {r} relations."
"message": "Deleting {n} features: {p} points, {l} lines, {a} areas, and {r} relations"
},
"tip": "Only redundant or nonexistent features should be deleted."
},
"missing_tag": {
"any": {
"message": "{feature} has no tags."
"message": "{feature} has no tags"
},
"descriptive": {
"message": "{feature} has no descriptive tags."
"message": "{feature} has no descriptive tags"
},
"specific": {
"message": "{feature} has no \"{tag}\" tag."
"message": "{feature} has no \"{tag}\" tag"
},
"tip": "Features must have tags that define what they are."
},
"old_multipolygon": {
"message": "{multipolygon} has misplaced tags.",
"message": "{multipolygon} has misplaced tags",
"tip": "Multipolygons should be tagged on their relation, not their outer way."
},
"tag_suggests_area": {