Issue Task Closed

#107759Utilize language domain mapping in extbase f:translate shorthand notation

Garvin Hicking 10/17/25, 12:06 updated 10/17/26, 14:41

Description

With #93334 merged, this allows to parse:

  <f:translate key="LLL:backend.layout:new_language" />

It would meet expectations that also this syntax should access the language domain:

  <f:translate key="backend.layout:new_language" />

A further improvement on top of this would be to allow this:

  <f:translate key="new_language" domain="backend.layout" />

for clear sepearation of what a key is, and where its domain lies. To prevent too many variations of what “key” can contain, maybe even introduce a new attribute to this like “domainkey”?

It needs to be kept in mind that also using the attribute “extensionKey” for f:translate would influence a shorthand notation and only refer to the extbase plugin scope and NOT the domain.

Reviews 3

History 510

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-10-20T21:50:07+00:00" > 10/20/25, 21:50 </span>

    Applied in changeset commit:daec7725c2a850b0dc1bfa0c60725380c9e666bd.

  2. Gerrit Code Review pushed patch set 1 for main to change 91253 status Resolved Under Review <span data-processor="relativetime" data-value="2025-10-26T11:01:10+00:00" > 10/26/25, 11:01 </span>

  3. Alexander Schnitzler commented <span data-processor="relativetime" data-value="2026-10-17T13:56:32+00:00" > 10/17/26, 13:56 </span>

    @benni Is there something left to do here? This ticket looks resolved. If so, what exactly is still open?