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
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: