Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move POT generation from gulp to tut #12

Open
bordoni opened this issue Nov 13, 2022 · 0 comments
Open

Move POT generation from gulp to tut #12

bordoni opened this issue Nov 13, 2022 · 0 comments

Comments

@bordoni
Copy link
Member

bordoni commented Nov 13, 2022

Currently, the generation of the base POT file happens on gulp pot, which causes problems and inconsistencies because it is not flexible enough to create separate files for translation, which is something we will need to improve how JS translations happen.

We can make gulp pot flexible for that purpose, but like in #10 I want to avoid including I18n tasks that require us to install all our Node Modules since these can be extremely time-consuming due to other dependencies on a plugin level.

I am just registering this particular issue here, as I am already working on a solution that makes use of the WP-CLI wp i18n command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant