Issue Task New Quiet

#109515Semantic of labels in Constant Editor

Xavier Perseguers 04/08/26, 13:14 updated 11/07/26, 16:06

Description

During our Huddle this morning with the localization team, and while going through pending approvals for French translations on Crowdin, I found what I consider wrong translations, namely that constant editor labels such as:

EXT:backend/Resources/Private/Language/locallang.xlf:config.loginLogo

Logo: Replace the TYPO3 logo above the login form (e.g. fileadmin/images/login-logo.png, EXT:my_theme/Resources/Public/Images/login-logo.png, or //domain.tld/login-logo.png).

EXT:backend/Resources/Private/Language/locallang.xlf:config.loginLogoAlt

Logo Alt-Text: Define the alternative text used as the alt attribute for the custom login logo image.

were suggested in French as a call-to-action or an imperative verb rather than a description of what the constant is used for.

So to make it clear, it was -translated-/suggested in a way that it means “[Please] replace the TYPO3 logo…” and “[Please] define the alternative text”. My understanding with all my years working with TYPO3 is that a constant is defined as a <label>: <description> value.

the screenshot in the documentation sounds like a description, rather than a call-to-action:

.clipboard-202604081502-dr3dj.png

Problems in the Core

First problem I found while reviewing the French suggestions was with

EXT:backend/Resources/Private/Language/locallang.xlf:config.loginFootnote

Footnote: Enter the text displayed on the login screen, for example to provide copyright information for the background image (e.g. background image © 2017 by John Doe) or a short description.

=> Clearly “enter” is a call-to-action, we cannot say as in the first two examples above that it’s some kind of description of the constant. Suggestion to rephrase to something like “Text to be displayed on the login screen, …” or “If set, this text will be displayed…”

Problems/conventions to be discussed

1. Do we agree on the meaning of the description text?
2. Should English verbs such as “Define […]” or “Replace […]” better be in the 3rd form? (Defines, Replaces)?
3. Shall we suggest to end the description with a period? (all the examples from EXT:backend have it, but the screenshot in the documentation does not).
4. Possibly more rules/clean-up to be thought of

I understand this will require time and effort to adapt, but it would help to have a consensus on those little tiny details so that translation work is easier and TYPO3 is even more polished.

If so, I would suggest to go through the various constant editor-related labels of EXT:backend first, and use this ticket as an umbrella ticket for future work.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[TASK] Semantic of labels in Constant Editor Resolves: #109515 Releases: main

Files 1

History 1

  1. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2026-11-07T16:06:51+00:00" > 11/07/26, 16:06 </span>

    Here I can share with you the rules I followed when I restructured the texts on Install Tool > Extension Configuration, Install Tool > Configuration Presets and Install Tool > Feature Toggles

    1. Use an action-oriented phrasing Verb (imperative) + object + optional context like Define […]” , “Replace […]” etc. (In fact I used the third person only for the CLI command descriptions)
    2. end phrases with .
    3. avoid filling words like “if set…”, “This setting…” (it is obvious that if it is set, the setting does something)
    4. prefer the active form to the passive form, except when you put the blame on the user or the product
    5. NEVER use exclamation marks.

    other criteria could be
    6. Always start with capital letter