You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider adding a way to automatically update the plugin's .pot file. If you decide to pursue this, of possible help are these Grunt tasks that scan a plugin's files for translation functions, then write their locations, internationalized strings, and accompanying messages (if any) in the .pot: https://www.npmjs.com/package/grunt-wp-i18n https://www.npmjs.com/package/grunt-pot
The POT generator makes a ton of sense, especially as that allows us to pull that step from our manual release process (example) and ensure it's handled automatically. The existing POT generator may be sufficient, though I can see where adding that into our plugin deploy action could be nice.
The existing Action looks like it may work just fine, it does seem like using the wp-cli command is correct because that actually picks up translations in JS files. I think the correct next step here is to test it (any takers?) and if it works as advertised, add that to an example workflow file.
@jeffpaul@helen
I am the author of WP Pot Generator and yes it uses WP-Cli to generate POT File.
But to be honest i haven't tested anything with Javascript file. i would be happy to update my action if it does not work with JS
Consider adding a way to automatically update the plugin's .pot file. If you decide to pursue this, of possible help are these Grunt tasks that scan a plugin's files for translation functions, then write their locations, internationalized strings, and accompanying messages (if any) in the .pot:
https://www.npmjs.com/package/grunt-wp-i18n
https://www.npmjs.com/package/grunt-pot
And here's a GitHub Action that may do the same:
WP Pot Generator
https://github.com/marketplace/actions/wp-pot-generator
Thanks.
The text was updated successfully, but these errors were encountered: