Why is there a hard link to [[Project:Licensing]]? Is it expected that every project has this redirect?
URL: https://translatewiki.net/wiki/MediaWiki:Fileimporter-file-contains-blocked-category-template/uk
Description
Description
Event Timeline
Comment Actions
I'm sorry, but what is the problem?
If the FileImporter extension is running on a wiki that doesn't want to validate licenses as we do it on Commons, that wiki should not enable the FileImporterCommonsHelperServer configuration (it's disabled by default). Nobody will ever see any of the messages about licensing then. But if it's set up, then yes, the extension assumes there is a project page about licensing.
Comment Actions
A project page about licensing can have different names in different wikis, e.g. the link https://uk.wikipedia.org/wiki/Project:Licensing leads nowhere because the correspondent page to Commons:Licensing is called Вікіпедія:Авторські_права in ukwiki. In ukwikisource it has slightly different name, Вікіджерела:Авторське_право. Therefore, while translating the unit, I can neither leave the original "Project:Licensing" nor use a translation that will be common across wikis.
Comment Actions
Perfectly there should be another interface message that supplies the page name. I won't be surprised if there actually already is one for the lincensing page. This way administrators can point it to the specific page without overriding the whole translation.
Comment Actions
Could you explain why this issue should not be fixed? It seems like a small almost trivial change to the extension to me, which would allow for localisation of that page name. If the main blocker is that you don't have the time/willingness to make this change, I am sure there will be someone else to volunteer.
Comment Actions
I'm afraid there is not much to add other than what was already said. As far as can tell this was never an actual problem for anybody, just a Translatewiki volunteer wondering. 3rd-party users shouldn't run into this in the first place. And even if, there are multiple easy workarounds. Adding the necessary code (which is not much, but not trivial either) and continuing to maintain it is not worth it if nobody needs it. Being a perfectionist myself I understand this is not perfect, but resources (including volunteer's resources) are scarce and need to be managed.