In Pakistan, Urdu is the most widely used and understood language.
However, players here are required to use English for nominations. As shown in the attached images, when I attempted to write a sentence in Urdu, the words were transformed into individual alphabets rather than remaining as complete words to form coherent sentences.
This bug not only disrupts the intended meaning but also poses a significant problem for local players. Many players here are more comfortable with Urdu and may not be as proficient in English. As a result, this issue could severely limit their ability to express themselves, participate in nominations, and fully engage with the community. The forced conversion of complete words into disjointed alphabets can lead to miscommunication and discourage participation, ultimately underrepresenting local playersâ contributions.
I kindly request that this issue be investigated further to ensure a more inclusive and accessible experience for all players.
Thank you in advance.
It seems that all left to right languages are broken for years already.
However, if you type it in correctly, to my understanding, despite the visual fail within Pokemon GO, wayfarer should display it correctly. Did I understand that correctly?
FYI: this could be an issue in Ingress as well. Weâre nominating Wayspots, not stops/gyms for PoGo or portals for Ingress. You may want to update the title of this thread to say Wayspots instead of Pokestops.
As far as Iâm aware, the bug doesnât exist with Arabic. At least not that Iâve seen in the years Iâve been reviewing nominations from Arabic-speaking countries.
It might just be that the bug got fixed for Arabic, being a widely spoken language, but that wasnât the case with less popular languages (Hebrew, Urdu, etc.)
Hi, thank you for your feedback. You describe a known issue with right-to-left language support that has already been brought up by communities who use these languages, and thank you for documenting yet another instance of this. Since this is the same bug I would like to merge your report to the existing bug thread by @SilverLyra regarding the same problem to reinforce that message and to hopefully attract more attention to this issue.