[5.x]: CP translations of sources not consistent

[LarsDol]

What happened?

Description

Hi! In our projects we tend to translate most of our the source titles in the Control Panel. The problem: labels of custom sources aren't translated consistently everywhere we'd like to see them translated. Most notably in two places: the page title you see your browser tab when navigating to the source and inside the pages/sources groups configuration panel.

Steps to reproduce

1. Create a new source or page inside the 'sources' configurator under Entries in the CP
2. As its label use a template translation string, like "source.singles" (which would translate to "Singles" (EN) or "Vaste pagina's" (NL)
3. Add the correct translation to the template string in your code (translations/en/site.php and translations/nl/site.php
4. Navigate to the created source inside the CP. You'll see that the browser's tab title isn't translated; also the labels on the 'pages' and 'sources' blocks aren't translated (this last one is less urgent as our users usually don't see this)

Expected behavior

See screenshots/description above

Actual behavior

See screenshots/description above

Hope this is something that's easily patched in an upcoming V5 version.

Thanks a lot for the great work!

Greetings,
Lars (Digital Natives Amsterdam)

Craft CMS version

Craft Pro 5.9.17

PHP version

8.4.19

Operating system and version

Linux 6.10.14-linuxkit

Database type and version

MySQL 8.4.5

Image driver and version

Imagick 3.8.1 (ImageMagick 7.1.1-43)

Installed plugins and versions

• Bugsnag | 5.0.1
• CKEditor | 5.3.1
• Content Buddy | 1.2.11
• Date Range Field | dev-main
• Formie | 3.1.18
• Neo | 5.5.7
• SEO | 5.1.21

[linear]

CMS-1924

[brandonkelly]

Thanks for reporting that!

It’s expected that source names within the Customize Sources modal aren’t translated, as that’s where the labels are defined. But the document title should be translated when a custom source is selected. Fixed that for the next release.

[brandonkelly]

Craft 5.9.18 is out with that fix. Thanks again!