Discussion/i18n: Localising blocks in FSE themes

[tomjn]

Currently for twentytwentytwo a workaround is being considered involving the core/pattern block in #33217 combined with use of __() when registering the pattern. While this achieves the goal it's a short term workaround.

For the longterm solution, I've created this issue to discuss.

[tomjn]

I've a suggestion!

Localised attributes:

    title: {
        type: 'string',
        localisable: true,
    },

with a textdomain attribute. WP can then run through each attribute, extract its value, and translate via the textdomain and pass the localised versions via filters, or swap the original value in the rendered string.

The textdomain would appear under the advanced panel alongside classes, with the intention that it wouldn't be used in post content, but somebody building templates in the site editor could make use of it.

The localisable flag would ensure that WP doesn't try to localise JSON, non-text values, or strings that shouldn't be localised such as a first name attribute or an address.

[jffng]

Thanks @tomjn , just linking a couple related issues:

#27402
#21204

[iandunn]

#21932 also seems related