Long ongoing reverse text bug with Hebrew

Bug Reports & Technical Support
,
1

Decided it may be a good time to revive this one from the old forum.

  • Description of the issue: when creating new submissions using either Pokemon Go or Ingress, while using Hebrew for typing titles/descriptions/supporting information, the text appears to be put in the reverse order (from left to right instead of from right to left). BUT, it’s only a visual illusion - if you go through with the process and submit the “reversed” text, it appears in the right order during reviews and on the in-game map, However, many submitters aren’t aware of this, and “pre-reverse” their text while submitting - which DOES cause the final product to be reversed - functionally gibberish - during reviews and on the game maps.

  • Date first (or most recently) experienced: several years. No exact start date known. Never stops.
    I’ve provided many examples of this in the old forum, but here’s one review I’ve encountered just now and prompted me to re-raise the issue. You can see the title appear in the right order in the nomination’s photo, and in the wrong order in the nomination’s title. (The description is reversed too.)

    image
    image852×544 98 KB

  • Device type, model, and operating system: irrelevant, occurs on all devices.

I’ll add that years ago, all Hebrew used to appear reversed on both PGo and ING, but at some point Niantic pushed a fix that corrected it all… EXCEPT for text typed during the nomination process, as I’ve described above. So it’s an issue Niantic DID partially fix in the past - the fix just needs to be extended to the nomination section too, and personally I’m baffled why it hasn’t been fixed yet, despite years of continuously reporting it.

6 Likes
2

I didn’t think I’ll be posting this kind of update, but funnily enough, while reviewing I stumbled across the exact kind of problem I’m trying to illustrate.
So the wayspot I’ve used in the original post got accepted - with the same jumbled text as I’ve shown (for the description too, but that’s not as obvious to non-speakers as the title).
Now obviously that prompted a title edit, which I’m currently reviewing…

image
image531×793 80.7 KB

…Except there’s a typo in the suggested edit too, so neither of the options are correct, and the edit did nothing except for stuff the local reviewing queue. Whether the edit gets accepted or rejected, more edits will follow sooner or later, and stuff the reviewing queue again.
Obviously, had Hebrew text been formatted right during the nomination process, all of this would’ve been avoided.
This is just one convenient example - there have been countless such cases over time.
All because of a completely preventable bug that, again, has been reported for years, and not fixed yet.