[wp-trac] [WordPress Trac] #52301: Blocks: Add i18n support to register_block_type_from_metadata

WordPress Trac noreply at wordpress.org
Thu Jan 14 17:45:35 UTC 2021


#52301: Blocks: Add i18n support to register_block_type_from_metadata
---------------------------------------------------+---------------------
 Reporter:  gziolo                                 |       Owner:  (none)
     Type:  enhancement                            |      Status:  new
 Priority:  normal                                 |   Milestone:  5.7
Component:  Editor                                 |     Version:  trunk
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:
---------------------------------------------------+---------------------
Description changed by gziolo:

Old description:

> Related issue in Gutenberg:
> https://github.com/WordPress/gutenberg/issues/23636.
>
> Related PR in WP-CLI from @swissspidy: https://github.com/wp-cli/i18n-
> command/pull/210.
>
> ## Description
>
> There are some issues related to internationalization (i18n) support in
> the introduced `block.json` metadata files that still need to be
> resolved.
>
> There is a proposal in block registration document that we still need to
> implement:
> https://github.com/WordPress/gutenberg/blob/master/docs/designers-
> developers/developers/block-api/block-metadata.md#internationalization-
> not-implemented
>
> The good news is that WP-CLI has implemented (https://github.com/wp-cli
> /i18n-command/pull/210) native support for translatable strings
> extraction from `block.json` file in `i18n` command. It was based on the
> aforementioned document.
>
> ## Code
>
> https://github.com/WordPress/wordpress-develop/pull/868

New description:

 Related issue in Gutenberg:
 https://github.com/WordPress/gutenberg/issues/23636.

 Related PR in WP-CLI from @swissspidy: https://github.com/wp-cli/i18n-
 command/pull/210.

 **Description**

 There are some issues related to internationalization (i18n) support in
 the introduced `block.json` metadata files that still need to be resolved.

 There is a proposal in block registration document that we still need to
 implement:
 https://github.com/WordPress/gutenberg/blob/master/docs/designers-
 developers/developers/block-api/block-metadata.md#internationalization-
 not-implemented

 The good news is that WP-CLI has implemented (https://github.com/wp-cli
 /i18n-command/pull/210) native support for translatable strings extraction
 from `block.json` file in `i18n` command. It was based on the
 aforementioned document.

 **Code**

 https://github.com/WordPress/wordpress-develop/pull/868

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52301#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list