As heavily explained in #152375: Implement translatable module names (with context),

neither human-readable nor internal names of modules and themes should be translated.

CommentFileSizeAuthor
#1 632896-rollback_translateable_module_names-2.patch651 bytesstborchert

Comments

stborchert’s picture

stborchert
he/him
Primary language German
commented
Status: Active » Needs review
StatusFileSize
new 632896-rollback_translateable_module_names-2.patch651 bytes

Is it really that simple?

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Yes ;)

We should additionally ensure the themes overview page as well as Update module's status report.

stborchert’s picture

stborchert
he/him
Primary language German
commented

The theme overview page doesn't seem to translate the names nor does the update overview.
So this should be the only part to change.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs review » Reviewed & tested by the community

oh? Thanks for verifying!

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Reviewed & tested by the community » Fixed

My, what a discussion! :)

Taking all the various opinions into account, I agree with those who have said that module names are proper names and they should not be translated. Aside from the "properness" of the names, it also seems like it will create a major support nightmare to have "Views" module called 28,000 different things depending on the language.

For someone who really needs these names to be translatable, I believe we have enough alter hooks (hook_system_info_alter(), hook_form_alter(), etc.) to accommodate them. But either way, for Drupal's default behaviour, I think rolling this back makes sense.

Therefore, committed to HEAD.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.