I don't think this counts as “tagging for the renderer”, which is more
about adding false data to “make the map look like what you want” (e.g.
“I want a blue line here, like the `route=ferry` line, so I'll use that”).
I think it could be very helpful for place names which aren't pronounced
the way you pronounce regular English words. e.g. in Ireland: “Dun
Laoghaire” [dun leary], “Tallaght” [tala], “Youghal” [yal], “Portlaoise”
[port leash]. This could be a problem even in England with places like
“Reading”, “Worchester”, “Cirencester”.
On 17/07/2019 00:54, Andrew Errington wrote:
I think this is a rendering issue (i.e. rendering speech instead of
graphics) and as such does not belong in OSM.
The work to convert an arbitrary string into speech belongs in the TTS
engine.
If we start putting IPA strings in OSM then we will start getting
arguments about the "correct" pronunciation. At the very least it is
tagging for the renderer, which we should avoid.
IMHO, of course.
Andrew
On Wed, Jul 17, 2019, 09:20 Greg Troxel <[email protected]
<mailto:[email protected]>> wrote:
John Whelan <[email protected] <mailto:[email protected]>>
writes:
> One or two are problematic usually as the street name is an
> abbreviation. For example 1e Avenue in French meaning First
Avenue.
>
> Any suggestions on how these should be handled? This particular
> application is aimed at partially sighted people but I feel we should
> be able to come up with a generic solution.
Two comments:
osm norms are to expand abbreviations, as I understand it. So that
should be fixed first
Even after that, we have ref tags, and there is often a road
whose ref
is something like "CT 2", "US 1", or "I 95". I don't really think
this should be expanded in the database. Instead, what's needed is a
table in the application, perhaps centrally maintained in OSM, of how
to pronounce standardize ref abbreviations. Putting phonetics of
"connecticut" on all use of CT or the expanded name is not
reasonable.
But I agree this needs help. I get told to turn on "Court 2" and "Ma
2". Luckily I understand this by now and it actually works ok. But it
does need fixing.
_______________________________________________
talk mailing list
[email protected] <mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/talk
_______________________________________________
talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk
_______________________________________________
talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk
