Changes between Version 2 and Version 3 of Ticket #42725
- Timestamp:
- 11/28/2017 08:00:05 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #42725 – Description
v2 v3 1 For years, the WordPress translators community has needed to resort to painful compromisesfor languages with grammatical gender, where women are often discriminated by default.1 For years, the WordPress translators community has needed to resort to '''painful compromises''' for languages with grammatical gender, where women are often discriminated by default. 2 2 3 3 From strings like `Lead Developer` to simply `Author` or `Editor`, some languages will always refer to these as males, regardless of the user self-identification. … … 17 17 - For simplicity purposes, `g()` '''assumes English will remain gender neutral,''' and so only takes one string as input. I'm happy to reconsider and let it have an optional three string input. 18 18 - `_gx()` would be trivial to add, `gn()` not so much. 19 - This proposal is part of my [https://2017.us.wordcamp.org/sessions/#wcorg-session-4139 WC US 2017 session]. 20 - Major props to @glueckpress for being a driving force in creating this with his [https://wordpress.tv/2017/06/27/caspar-hubinger-big-little-shame-a-tale-of-empowered-user-experience-through-localisation/ WC Europe 2017 talk]. 19 21 20 - This proposal is part of my [https://2017.us.wordcamp.org/sessions/#wcorg-session-4139 WC US 2017 session].21