Standardized message for "Translation administrator"

I was surprised to discover that there is no standardized message for "Translation administrator" in the Translate extension.

For Wikimedia, there's Group-translationadmin-member in Wikimedia Messages. For translatewiki, there's Group-transadmin-member, which is not assigned to any group.

Such a role is probably needed on every site with this extension. Shouldn't it be a part of the extension?

I think you are speaking here about the message for an individual user member of the group. That "*-member" message is normally NOT capitalized and singular: "translation administrator", unlike the name of groups (which is also the names of description pages or categories on the target wiki, which are translated according to the default language of the wiki and not the user-selected UI language).

That's why there are different messages even if they are closely related. Note also that for some languages, some wikis chose to use "neutral" ("épicène" in French) notation showing mixed a masculine+feminine form as much as possible, notably for messages showing a plural form, but sometimes as well for the explicit "neutral" gender (used by default for users that don't want to specify it in their preferences, or that have not set it, and generally selected for bot accounts).

This "neutral" form is sometimes the subject of debates, e.g. in French, because some users don't like the "épicène" orthography and still prefer seeing a "traditional" form (where the masculine gender "wins" over the feminine when there are mixed genders): they don't like seeing "administra·teur·trice" for example, but they accept the "(e)" or "(s)" suffixes to mark an optional feminine or plural... where it can apply. For longer messages, we sometimes prefer "administrateur ou administratrice" without using such "épicène" notation.

For such case, and to close some debates, may be we'd need variants in French for "trad" and "reformed", like they exist in German, Dutch or Spanish for "formal" and "informal". However such variants are still not registered in BCP47, which just lists variants for the orthographic variants (with a string community preference to keep the "traditional" orthography before the debated 1990 reform. For now French in MediaWiki doesn't use any variant. because the traditional ortography is STILL valid after that reform and can be accepted by everyone. In my opinion the "épycène" variant should not be the default (as it requires the addition of an unusual "middle point" punctuation that is not present on most French keyboards, and that notation confuses most text search engines and spell checkers; as well that "épycène" notation currently has no supporting standard, it is too recent in the history of the language but most frequently appears now in pages related to LGBTQ+ rights or feminism, that are politically/socially oriented and sometimes their usage cause new "hot" debates and bad online behaviors).

Like you, I strongly support closing the "gender gap" in wikis and open projects in general, i.e. including with more women.

(notably to show to males that women are accepted and have a voice to be heard including for decision processes, or page design, color choices, skins: let's stop the universal blue/gray used everywhere, we can all live even if there's some pink/purple or more colors, or some floral decorations... as long as we preserve or improve accessibility for color-impaired users with appropriate skins or features available to them; as well we must preserve the compatiblity for blind readers, users that prefer dark backgrounds, to save energy on their mobile device, and "redshifted" colors with reduced contrast when looking at pages in dark environments, to reduce the physical stress on eye).

But not at the price of inventing a new "neutral" gender (which does not event exists legally for now and that has compeltely disappeared from French since many centuries): as much as possible, we should use traditional forms with "or" conjunctions, except in very few messages that need to remain very short (but where the new "épicène" notation should be avoided by default, especially for plurals including with mixed genders). So solving the "gender gap" should only occur in translatable messages for referencing a single user (with the "GENDER:" parser function and a given local user name, but avoiding the "épicène" notation for the "unknown/unspecified/prefer not to say/non human/bot" case); however there's no restriction to do or enforce for content pages that will use the appropriate form for their discussed topic (and that should not need to use the UI language preferences of the currently reading user).