Currently, mostly "mediawiki general or unknown" is auto-selected. Since more precise group informatin is available in TWN anyway, and links inside twn can sometimes be used to guess message groups, that data, or related data, should be used for more precise presets.
Description
Description
Event Timeline
Comment Actions
I'd love to see that but how to achieve this? We don't even have a "proper" linking between Phabricator projects (for task tracking in Maniphest) and code repository names, or extension homepages on mediawiki.org. So I don't see any way to provide that... :(
Comment Actions
...plus what about those projects on translatewiki.net that do not use Wikimedia Phabricator for issue tracking? Hmm.
Comment Actions
These have their own links. I suspect without knowing that twn has a list of mappings per (non-aggregate) message group - likely with a default "mediawiki-default-or-unknown" for most.
If I am wrong, the way to go could be to introduce and populate such a list.
Comment Actions
Last time I mass-filed tasks for Wikimedia-deployed extensions, I think 80% had a project matching the #mediawiki-extensions-{name} format where {name} was the git repo name. Definitely not perfect, but probably a good enough start?
Comment Actions
Logical place for this information would be extension.json. composer.json has support.issues which is not directly usable and not all extensions will be using composer.json.
Comment Actions
@Nikerabbit: If I see it right, Translate is currently not using extension.json either.
As of yet, I could not find where and how the support link is generated. resources/js/ext.translate.editor.js prepares the HTML a element for it but not its href contents.
If we had something like support.issues or support.issues.i18n in extension.json to override the current default, then it would have to contain at least a placeholder for the message ID, possibly more.
Comment Actions
Per Nikerabbit, feel free to reopen when all extensions store their issue tracker URL/component in a composer.json file in their repository.
Comment Actions
Thank you Nemo.
I first had been a upset when I saw several of my proposals towards enhancing the questions regarding message internationalization and documentation closed one after the other. That is why I did not reply at once. I had in my mind anyways to make happen what is needed but unfortunately could not figure out enough of it. So, I need help. Anyways, Thank you for not declining my proposal outright.