Closed bonakor closed 1 year ago
See #3081, which I think we can merge now that WP-CLI released a new version
cc @strarsis
Yes, using wp i18n
instead eliminates the need for extra tools and also adds proper Blade-PHP parsing.
The current release of wp i18n
has some bugs though. There had been no new release with the bug fixes yet.
But one can install the latest wp i18n
that works properly by using wp cli update --nightly
.
This may be mentioned in the documentation until wp i18n
has a new stable release.
Sorry, I didn't realize https://github.com/roots/sage/pull/3081 fixed it already. While wp-cli team handles the remaining bug, should this PR be merged as it has the working solution proposed in the docs? Or are the docs enough?
The yarn command was not able to really create a complete pot file. Most strings from the Blade templates were missing. With this command, it seems to be working as it should be.
I found the command in the docs https://docs.roots.io/sage/10.x/localization/#generating-language-files
I removed the previous command to avoid any misunderstanding.