It's unclear whether FileExporter and FileImporter extension name messages should be translatable or not
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Amire80
	Dec 12 2017, 1:08 PM

Description

In translatewiki I see these two messages:

Both are the extension name. In qqq they are tagged as "optional", but they are not configured as such in the translatewiki configuration files.

It's also strange that any special handling is needed for them at all, because all extensions have a name.

I can imagine these ways to resolve this, but both require understanding of how the extensions work:

Explaining why they exist as distinct messages in qqq and where are they used (if they are used anywhere other than in Special:Version).
- It may also make sense to configure them as optional in translatewiki group config files.
- Contrariwise, it may make sense to encourage people to translate them as generic names, like it's done with ContentTranslation, UploadWizard, VisualEditor, etc., and they shouldn't be marked as optional.
Removing them completely.

And maybe it's something else entirely.

Event Timeline

Amire80 created this task.Dec 12 2017, 1:08 PM

Restricted Application added a project: TCB-Team (now WMDE-TechWish). · View Herald TranscriptDec 12 2017, 1:08 PM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Explaining why they exist as distinct messages in qqq and where are they used (if they are used anywhere other than in Special:Version).

They are used only in extension.json which afaik will only show them on Special:Version.

namemsg": "fileimporter",

I'm not really sure in what cases we should be using a namemsg here and in what cases we should be hard coding a string in en?

I think it's okay to make the extension name translatable. For most extensions they should be treated as proper names and thus be optional. For generic names it helps to not mark them optional.

Lea_WMDE moved this task from Backlog to Tickets in sprint on the Move-Files-To-Commons board.Feb 13 2018, 3:59 PM

Se we also have this message key for RevisionSlider https://github.com/wikimedia/mediawiki-extensions-RevisionSlider/blob/master/extension.json#L13 and a provided en name https://github.com/wikimedia/mediawiki-extensions-RevisionSlider/blob/master/extension.json#L2
This is the same situation as FileImporter

I'm slightly confused about who should act further on this ticket!
Is this something we need to change on translatewiki? or?

Tobi_WMDE_SW moved this task from Tickets in sprint to Watching on the Move-Files-To-Commons board.Feb 13 2018, 4:26 PM

thiemowmde moved this task from Incoming to Move files to Commons on the TCB-Team (now WMDE-TechWish) board.May 11 2018, 5:05 PM

Contrariwise, it may make sense to encourage people to translate them as generic names

This is the best option in my opinion. This means not claiming them to be optional in message documentation.

Nikerabbit moved this task from Backlog to External on the translatewiki.net board.Jun 17 2018, 4:46 PM

thiemowmde removed a project: TCB-Team (now WMDE-TechWish).Jan 7 2022, 2:57 PM

I think status quo is good enough, given the lack of interested on this ticket.

Messages using the pattern skinname-* or *-extensionname are automatically treated as optional. The {{optional}} template is just documentation and does not affect the property.

It's unclear whether FileExporter and FileImporter extension name messages should be translatable or notClosed, ResolvedPublicActions

Description

Event Timeline

It's unclear whether FileExporter and FileImporter extension name messages should be translatable or not
Closed, ResolvedPublic
Actions