Active
Project:
Drupal core
Version:
main
Component:
single-directory components
Priority:
Major
Category:
Feature request
Assigned:
Reporter:
Created:
11 Dec 2024 at 02:28 UTC
Updated:
10 Feb 2026 at 08:23 UTC
Jump to comment: Most recent
Comments
Comment #2
griffynh commentedComment #3
wim leersComment #4
wim leersComment #5
wim leersDoes UI Patterns have a solution for this, similar to #3493070-4: SDC `enum` props should have translatable labels: use `meta:enum`? 🤞
Comment #6
penyaskitoNow that #3390712: Add component variants to SDC landed, we will have the same problem there.
Whatever we end up doing here, should be done for variants.
It might not be strictly consistent with e.g.
meta:enums, but IMHO they are different enough usecases to justify that.Comment #7
wim leersComment #8
phenaproximaI wonder if this could dovetail with the work being done to make config actions translatable? The current approach proposes adding a
!translateYAML tag, which presumably would allow potx to find the strings that need to be translated for a project (which would include recipes and, potentially, themes that expose SDCs).Comment #10
svendecabooterIt would be good if we could use the same logic for translating recipe input / config actions, and apply it to SDCs.
So that would make this issue postponed on the recipe one, which seems to need quite some work still..
Are the same outstanding issues for recipes also applicable here (monolingual non-English / multilingual non-English)? Or not, because the SDCs are not config objects?