Hi @Huji,

Thank you for filling this request! I understand that localisation support would definitely be great to have there, especially given this functionality exists for similar parts of MediaWiki (such as special page aliases or namespace names). Unfortunately, CommunityConfiguration currently doesn't support provider localisation, and it seems it would be a fairly complex project to add it.

For namespaces/special page aliases, we have *.namespaces.php and *.aliases.php files, which are defined via wgExtensionMessagesFiles. We would need a similar mechanism here. According to wgExtensionMessagesFiles's documentation, extension message files can be only used to (re)define what is provided by languages/messages/MessagesEn.php (and equivalent for all other languages). Since those are additional identifiers (that Core, and consequently MessagesEn.php, has no awareness or knowledge of), it seems like this mechanism wouldn't be usable.

The other option that comes to my mind is engineering a similar and parallel system (which would be specific to CC-owned identifiers). Although that would resolve the problem, other extensions have similar needs. For example, GrowthExperiments has pages such as Special:ManageMentors/add-mentor, where only the first part of the page name is localizable. Implementing basically the exact same feature in multiple extensions seems like a bad idea (and is pretty much exactly why CommunityConfiguration was created).

Building a general-purpose system for localising subpage names seems to be quite an initiative, and larger than what the Growth team currently has the capacity for. If there is an easier solution or a quicker win you (or anyone else) is aware of, I'd appreciate if you commented on the task, we'd be very happy to consider it.

Best regards,
Martin Urbanec