sketch wrote:"Penn" should say "penn", but do we want "Penn." to say "Pennsylvania"?
GizmoGuy411 wrote:Therefore we may need to follow suite for the letters used for Roman Numerals too.
GizmoGuy411 wrote:So maybe Roman Numerals could use a period after them instead of quotes to differentiate them.
sketch wrote:Street names should still match signs. If it says "Louis XIV" use "Louis XIV". No one is going to think to search for their aunt's house at 1234 Louis The 14th St", and it's going to look wrong on the client display.
GizmoGuy411 wrote:I agree with sketch in that I am really not very concerned about Roman Numerals and that the letters themselves are more important at least for North America using the English voices.
GizmoGuy411 wrote:What I am MORE concerned with is why these variations exist in the first place and if they are indicators of some bad RegEx that needs to be addressed at the Waze end, as other parts of the world may need Roman Numerals.
GizmoGuy411 wrote:Actually I don't think there are many more instances than those I listed as potential conflicts with Roman Numerals. This was limited to valid Roman Numerals, not simply every possible combination of letters used in Roman Numerals. I'll edit that in the prior post.
sketch wrote:Unless "Louis" is pronounced neither the English nor the French way, it cannot be "fixed". In some places one will be right, and in others the other, but no universal fix is possible.
sketch wrote:BGSes usually use the old-fashioned abbreviations, and I think it'd be nice to include those, with periods only, as TTS abbreviations – for example Ala. for Alabama, La. for Louisiana, Calif. for California, Penna. and/or Pa. for Pennsylvania, and so forth.
Users browsing this forum: No registered users