TTS: Destinations listing cut (probably because of slash '/') about osmand

[vmicho]

wow that was fast. From the commit, it looks like reasonable fix ;)

[sonora]

Yes, a lot of TTS engines have issues with slashs, at least used to, some time ago. But we replace by a comma before passing it on. Will need to investigate closer , at first sight it's odd.

EDIT: Upon a quick test I can confirm that the TTS engine receives the text with the slash behind "Biel" replaced by a comma ok, but also truncated behind it, so there seems an issue before the character replacement.

EDIT 2: Upon further inspection, it seems by design. Looks like we shorten destination announcements to 3, probably makes sense to avoid endless reading of navigation prompts. So the only bug to fixing here is we should shorten first, then do the comma replacement, to avoid cutting between words which belong together.

[sonora]

Fixed here: ec91a71. Thanks for reporting!