Hi Cyrille,
We’ve checked the plugin with the Plugin Check tool and aren’t seeing any outstanding i18n issues on our side, and strings seem to be being extracted correctly from what we can tell on translate.wordpress.org?
We don’t include .po or .mo files with our plugins because strings are extracted automatically?
Could you please let us know what error you are experiencing exactly?
Thanks!
Oliver
Hi Oliver,
My assumption was incorrect. Actually, it seems that some chains are not being taken into account. Those found in the right sidebar of a block.
Examples:
- Overlay menu on scroll
- Expandable modal submenus
- Use first link in block to link entire block
Could you fix this?
Thank you,
Ah! Those are all in block-options.js and are all wrapped in the __() function so either the way we’re including the JS is preventing the translations from being picked up or they’re being picked up but the __() function isn’t working.
I’ve had a look on translate.wordpress.org and it looks like all the translation strings you mention are there so this makes me think that we’re not enqueuing the JS file with the correct dependancy array.
I’ll get this checked and tested and hopefully there’ll be a fix for you soon!
Thanks for highlighting!
Oliver
Alors ! J’ai trouvé le problème 🙂
This issue should now be resolved in v1.4.4 that I just pushed out.
Oliver
