Consider the ideal approach for text localization

[t-hamano]

When you save changes, if you check "Localize Text", the template content will be saved as a pattern and translation functions (esc_html_e()) will be applied to some of the text:

The text that gets replaced is determined by a hard-coded list of regular expressions and blocks.

As a result, there have been reported issues with anything that doesn't fit these not being localized:

• Label, Placeholder, Button Text in Search block don't become translation ready #737
• Labels in Pagination block don't become translation ready. #742
• Labels in Comments Pagination block don't become translation ready. #773
• moreText in Excerpt block isn't internationalised #744
• Summary text in Details block needs to be internationalised #756

Maintaining this hard-coded data is impractical.

Perhaps a more generic approach is needed, although this has probably been considered in the past.

[iamtakashi]

Thanks for looking into it, @t-hamano! I hope this gets sorted soon. It's a pain to do this manually in every theme 😅

[iamtakashi]

Hi @t-hamano, I'm curious about the plan for this. I'm all for a new approach, but at the same time, we want to help the people who work on themes every day because missing internationalisation for those blocks comes up very often.

[t-hamano]

Unfortunately, I don't have enough time to solve this problem right now, and I don't have a concrete answer as to what the ideal approach would be to solve this problem.

[iamtakashi]

Okay, should we then reopen all the issues that were closed due to this initiative?