Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
As heavily explained in #152375: Implement translatable module names (with context),
neither human-readable nor internal names of modules and themes should be translated.
Comment | File | Size | Author |
---|---|---|---|
#1 | 632896-rollback_translateable_module_names-2.patch | 651 bytes | stBorchert |
Comments
Comment #1
stBorchertIs it really that simple?
Comment #2
sunYes ;)
We should additionally ensure the themes overview page as well as Update module's status report.
Comment #3
stBorchertThe theme overview page doesn't seem to translate the names nor does the update overview.
So this should be the only part to change.
Comment #4
sunoh? Thanks for verifying!
Comment #5
webchickMy, 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.