Illia Sanz

For core plugin – you do not need to use .pot file and json, it’s made automatically on WP translation page. For other plugins – you will need generated .pot file.

I understand that localization is complex, so I made tutorial. Also, I updated localization file for addons, so you don’t need to generate it, just copy and rename

Tutorial is here https://greenshiftwp.com/documentation/greenshift-extra/translation-of-custom-gutenberg-wordpress-plugin/

I tested for some languages and it’s working for me. I hope this helps

the only thing which I see, that WP repository didn’t unpack file for blocks, even if it has correct registration, I will write to Gutenberg issues https://cleanshot.com/share/DYfYLrdT But this is not what we can change, it’s bug of repository

With all respect, I recommend to study question first before blaming that we do something wrong. As I wrote, I can provide you source file and you will see that everything is correct

This is example https://cleanshot.com/share/PcDzyKjG

1175 fields – this is correct, this is how much strings are in JS files. JS translation is working not the same as PHP. It’s packed by webpack, then unpacked via i18n package and wp_set_script_translations. On plugins hosted on wp.org, i18n package is automatically unpack strings and you have them https://translate.ww.wp.xz.cn/projects/wp-plugins/greenshift-animation-and-page-builder-blocks/

On Custom blocks not hosted on wp.org, you need to do this manually. This is example how to do this https://devmaverick.com/how-to-translate-a-custom-wordpress-gutenberg-block/

Why only 1175 fields? Because JS and PHP have different way to translate and different localization files. PHP strings can be translated from .pot file that is placed in lang folder (and languages folder in premium addons).

Of course, Gutenberg should have more simple translation way for JS and this was discussed for years but currently the only way is still to generate custom json via i18n. If you provide me this json file for your language I will be glad to include it in plugin

Here is another good article https://awhitepixel.com/wordpress-gutenberg-create-custom-block-part-8-translation/

Thank you for your review, however let me disagree. First of all, of course, all of our plugins have correct usage of __(“text”, “textdomain”). We have zero non translated strings. There are just few of them that should not be translated like names of libraries, etc.

Also, of course, you can simply search by pattern (__””) and you will see that all strings also have textdomain.

Yes, you reported this years ago but it’s not our fault that wordpress still has no good translation for third party addons for gutenberg. You can translate plugin by using next tutorial https://developer.ww.wp.xz.cn/block-editor/contributors/localizing/ It’s quite complex for gutenberg and requires to use terminal, but again, it’s not our fault.

I am ready to provide you source file of one of our addon so you can see that from our side everything is correct, all strings are translated. I hope you will change rating after this

if you use Row, it has Gap option, it’s first option in Row settings

I don’t know how you added block, but you need to add margin top as 0 on it

I see, but these bars are added by Youtube itself, not by our plugin. Problem is that you set 3:2 ratio for video for mobiles, but youtube has no such ratio so it’s trying to fill the gap by adding these bars