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.dbraughlr wrote:From what you listed, there are thousands of them. That's clutter.GizmoGuy411 wrote:Therefore we may need to follow suite for the letters used for Roman Numerals too.
What range do you really intend to cover?
That doesn't seem likely, at least not if you intend to cover a range beyond 1 to 30.GizmoGuy411 wrote: So maybe Roman Numerals could use a period after them instead of quotes to differentiate them.
What's wrong with using Louis the 14th instead of Louis XIV.? If anything, our experience with N/E/S/W should tell us that it was a bad precedent that should not be expanded.
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.
So any submission I may to Waze at this point will be to just point out the inconsistencies. We have plenty of one off issues with TTS pronunciation that is something that may be able to be adjusted in the future via the editor on an individual basis.
Issues like "Sulgrave Dr" being pronounced in the past as "Sulgrave Doctor" however where of concern as in this case it may have been indicative of a wider problem that could effect other names as Doctor vs Drive was more of a global concern.
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.
Not sure I agree with you that there are thousands of RN combinations, as many combinations of the letters in RNs are not actually valid RNs.
Re: Roman numerals