Custom block translations are not hit by wp_set_script_translations.

[shimotomoki]

The following plugins are hosted on WordPress.org.

Plugin Directory
​https://wordpress.org/plugins/flip-box-block/
The plugin has been updated in Stable and 0.1.31 can be obtained from the Advanced tab.
​https://wordpress.org/plugins/flip-box-block/advanced/
Source Code
​https://github.com/shimotmk/flipbox-block

I am having trouble getting my JavaScript translated text to translate.

Translating WordPress contains the text translated by JavaScript.
(This is an example of Japanese)
​https://translate.wordpress.org/projects/wp-plugins/flip-box-block/dev/ja/default/

However, when I install the plugin and set the language to Japanese, the translation is not done.

Is this a problem with the plugin code?
Or is there a problem with the WordPress.org translation (GlotPress) ?

[dd32]

​https://plugins.trac.wordpress.org/browser/flip-box-block/trunk/readme.txt?marks=7 still specifies 0.1.21 as the latest version, so 0.1.31 isn't stable / being built.

The last language pack built for the plugin was 0.1.6, that contains the flip-box-block-ja-fe9085f3d98a08dce07b16c5b89041e9.json JS translations.

It looks like the textdomain you're passing to wp.i18n.__() might be flipbox-block which isn not the slug on WordPress.org, which would be the textdomain used for the language pack. That's probably a problem, as WordPress doesn't know that textdomain is the WordPress.org language pack.

I'm not seeing any issues on the WordPress.org side here, so this is likely an issue with the plugin. Meta trac isn't the appropriate place for developer support, one of these will likely help:

• ​https://wordpress.org/support/forum/wp-advanced/
• ​https://developer.wordpress.org/plugins/internationalization/
• ​https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#handling-javascript-files

[shimotomoki]

@dd32
Thanks for your comment.

I bumped the version by saying that it wasn't translated in Stable, but it wasn't resolved.

I also posted on Developing with WordPress.
​https://wordpress.org/support/topic/custom-block-translations-are-not-hit-by-wp_set_script_translations/#new-topic-0