IlDucci
commented
4 years ago This error has persisted over the last year. While the punctuation part can sound like nitpicking, the misreading seems to be heavily implied to be an issue related with the encoding used by RetroArch when feeding texts to Windows 10's Cortana.
Description
I've done some tests of the Accessibility Narrator on Windows 10, with Spanish (Spain) Cortana, and I've found a couple of minor issues.
Expected behavior
When moving the menu to a menu line that contains accented characters, the narrator should read them properly, reading stuff like "Energía" or "Listas de reproducción".
When reading a Settings function that has an On/Off switch, the switch should read something like, "Accessibilidad activado" or, hopefully, "Accessibilidad activada".
When the Narrator reads a long Setting, it should read each element with a punctuation separator, like a comma or a colon. "Ajustes, Interfaz de usuario, Vistas"
Actual behavior
When moving the menu to a menu line that contains accented characters, the narrator doesn't identify them properly, reading "Energía" as "Energa" or "Listas de reproducción" as "Listas de reproducc-superíndice3 (note: that's ³)-n". Seems like there's a text encoding issue.
Also, when reading a Settings function that has an On/Off switch, the switch is read in English, as on or off, instead of using a translatable equivalent.
Reading a long Settings line will cause the Narrator to read it like it's a long, unpunctuated line. "Ajustes interfaz de usuario vistas".
Steps to reproduce the bug
Bisect Results
Version/Commit
Environment information
Additional comments
If you want to avoid the huge can of worms that is adding a custom on/off line per option line and per language to make sure each setting has the properly gendered, you could make the Narrator say something like: "Setting: Setting Enabled/Disabled". For example, "Accessibility Enable: Setting Enabled".