Thanks for pointing this out — I was running into a similar issue with some strings not being properly translated due to improper usage of esc_html() before __() or _e().
While debugging a translation issue for a fan-based project, I realized some strings were escaping HTML before being passed to translation functions, which caused them not to show up in the .po file. It’s especially important in multilingual environments or community-based apps where localization is key.
In my case, I noticed this while working on the iOS page of a Brawl Stars mod site. If anyone wants to check how we’re handling strings and translations properly now, here’s the iOS section of the project:
👉 https://nulls-brawl.com.de/nulls-brawl-ios/
Hope this helps others facing similar issues. Always escape after translation functions, not before!
