[wp-meta] [Making WordPress.org] #5779: theme.json strings not extracted for translation

Making WordPress.org noreply at wordpress.org
Fri Dec 3 09:42:55 UTC 2021

#5779: theme.json strings not extracted for translation
 Reporter:  oandregal                 |       Owner:  (none)
     Type:  task                      |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  worksforme
 Keywords:                            |
Changes (by oandregal):

 * status:  reopened => closed
 * resolution:   => worksforme


 The internationalization process is working as expected, so I'm going to
 close it (not sure why I can't mark this as "fixed" so I'm marking it as

 I've been looking at this with the help of @akirk and this is what

 - How to search for strings coming from "theme.json":
   - term: "theme.json"
   - term scope: "any"
   - status: "Current/waiting/fuzzy + untranslated (All)". This is
 important. I've used "any" in some searches, which doesn't show you the
 strings for which there's no translation (so I wasn't getting results when
 there were some). This explains the weird results I got for Gutenberg.

 Doing that search I can confirm Gutenberg and other themes with theme.json
 I've checked work as expected, such as BlockBase and Mayland (blocks).

 Now, there's a different issue with a few themes that also have
 theme.json: their latest submission happened ''before'' the i18n process
 was set up to extract strings coming from theme.json. Hence, they don't
 have any strings coming from that source. This is the case of TT1-blocks
 and Armando, for example. As soon as they publish an update to the repo,
 the strings should come up.

Ticket URL: <https://meta.trac.wordpress.org/ticket/5779#comment:11>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list