Add a way to identify module/theme/profile names as unique translation strings

Created on 18 December 2016, over 8 years ago
Updated 15 May 2025, 2 days ago

Problem/Motivation

While translating Drupal core to Dutch during a Dutch translation sprint, it occurred to us that it is very hard to determine whether a word as 'Standard' is used as module name or as regular text.

We decided to keep module/theme/profile names as-is and to not translate these. However, currently this seems impossible. For example; when we talk about the Views module, we expect the module name on the module overview page to be Views. However, the Views page title should be 'Overzichten'.

Steps to reproduce

Proposed resolution

Would it be possible to add a context to the t() function everywhere we use a module name?

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component

language system

Created by

🇳🇱Netherlands BarisW Amsterdam

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇦🇺Australia mstrelan

    Seems like a good idea. I guess the first step is to identify all the places the context is missing.

    Added the issue template. Not sure this is related to "system.module", changing component to "language system".

Production build 0.71.5 2024