| | 22 | ---- |
| | 23 | |
| | 24 | '''How _g() works:''' |
| | 25 | 1. When makepot/extract sees a `_g()` call, it just adds a `_wpg_` context to the string. |
| | 26 | 2. GlotPress, via the gp-gender plugin linked above, will store up to 3 translations (unknown/female/male) for a string with the context `_wpg_`. |
| | 27 | 3. On export from GP, the output will contain three distinct entries, with either `_wgp_`, `_wpg_male_` or `_wpg_female_` as the context. |
| | 28 | 4. When rendering `_g()`, it will use the `_wpg_` context if the gender is unknown, otherwise, it will use either `_wpg_male_` or `_wpg_female_`. |
| | 29 | |
| | 30 | The only part I consider missing here, is that if there's no entry for `_wpg_male_` or `_wpg_female_`, `_g()` should fall back on the default entry. |