Lisa Hernandez3 said:But since the app was translated into American English, it was supposedly tailored for users in our linguistic region (though I'm not entirely sure which specific parts still feel off, but those are minor details). So, whoever handled the localization probably didn't anticipate that gender would be such a factor within the post itself. Maybe they weren't being intentional, or maybe they were just following standard industry practice.
Btw, regarding that instance where a moderator couldn't tell which gender a user belonged to—honestly, I doubt it would have helped even if their gender had been clearly labeled. Confusion in addressing people happens regardless of whether you underline or highlight their gender a hundred times. And, in my opinion, these little mix-ups are less offensive or significant—they're mostly just communication hiccups—compared to the issues that might arise if the forum were viewed as a population strictly divided into men, women, and non-binary individuals. Why? Well, just look at the original post again.
But hey, it’s fine if you don't see things through that lens.
Whoever did the localization did a sloppy, rushed job just so it would superficially look like American English. The evidence is everywhere. Just look at how some controls are in English while others are translated.
Those things are easy enough to fix. The issues I'm talking about are much harder because the app's design doesn't account for them. The reason is that American English grammar has fundamental differences compared to how we structure things here.
Here are two quick examples:
"The number of messages in Inbox is 17."
"Inbox (17 Messages)"
In the first example—incorrect grammar. The app's architecture doesn't support proper declension.
In the second, there isn't support for different plural forms which exist in our language but not in English. And it goes deeper than that. Even singular nouns can appear in plural contexts.
(1 message
s, 2 message
s, 3 message
s, 4 message
s, 5 message
s, ..., 21 message
s, 22 message
s, ...)
Essentially, these aren't just different plural forms. It's about how the case changes based on the number. With 1, you need a specific form; with 2, 3, and 4, it's one thing; and with 5 through 10 or 11 through 14, it's another. This happens regardless of the digit preceding it. But I'll leave the linguistics to the experts... Regardless, it's fundamentally different from English, where everything after 1 is simply plural.
It is impossible to fix these issues without digging deep into the app's core code.
Anyway, back to the point. 😁 We clearly see this differently, so let's just leave it at that. 🙂