Strings from Blade-syntaxt don't show up in sage.pot

el_skak · July 8, 2022, 11:07am

Hi,
Im having an issue translating my theme. My strings wont appear in the ./resources/lang/sage.pot file in my theme-folder.

I have these four test-strings in my theme:

{{ __('translate me from Blade 1', 'sage') }}
{!! __('translate me from Blade 2', 'sage') !!}

@php
  echo __('translate me from PHP 1', 'sage');
@endphp
<?php
  echo __('translate me from PHP 2', 'sage');  
?>

When I run 'yarn translate' only the string “translate me from PHP 2’” will appear. Which is the only one in plain ol’ php.

First I thought that my WP-CLI was outdated, but now I am on the latest version.

Do you guys had same experience?

Here is my package.json:

"scripts": {
    "dev": "bud dev",
    "build": "bud build",
    "translate": "yarn translate:pot && yarn translate:update",
    "translate:pot": "wp i18n make-pot . ./resources/lang/sage.pot --include=\"app,resources\"",
    "translate:update": "for filename in ./resources/lang/*.po; do msgmerge -U $filename ./resources/lang/sage.pot; done; rm -f ./resources/lang/*.po~",
    "translate:compile": "yarn translate:mo && yarn translate:js",
    "translate:js": "wp i18n make-json ./resources/lang --pretty-print",
    "translate:mo": "wp i18n make-mo ./resources/lang ./resources/lang"
  },

I DO get a small error when the script runs the translate:update command. But I dont think that is causing the issue.

strarsis · July 8, 2022, 8:29pm

You need wp i18n release 2.3.0 for the Blade-PHP language feature:

github.com/wp-cli/i18n-command

Add support for PHP-Blade files

wp-cli:main ← strarsis:add-blade-extractor

opened 02:46AM - 21 Feb 22 UTC

strarsis

+341 -4

This PR adds the code and (simple) tests for extracting translations strings fro…m PHP-Blade template files. Luckily the [`4.x` branch of the `gettext` project already contains a fully working PHP-Blade Extractor](https://github.com/php-gettext/Gettext/blob/4.x/src/Extractors/Blade.php), which can be used very similarly to the PHP extractor for `wp i18n`. The `IterableCodeExtractor` file filter [had to be refactored](https://github.com/wp-cli/i18n-command/pull/304/files#diff-6dbbabe411870b35fac549f92d2c059e9cc16d2f0f85b37347393150a9f3e7c1) a bit to make it also support filtering for multiple file extensions (as it is the case with `blade.php` for PHP-Blade template files). The ~~`illuminate/view`~~ `BladeOne` compiler for a standalone PHP-Blade compiler [had to be included as `composer` dependency](https://github.com/wp-cli/i18n-command/pull/304/files#diff-d2ab9925cad7eac58e0ff4cc0d251a937ecf49e4b6bf57f8b95aab76648a9d34R15) as the `gettext` package doesn't require it on its own/expects a PHP-Blade compiler to be available. Edit: Because of current PHP version constraints by `i18n`, a release of another, standalone and well-maintained PHP-Blade compiler is used instead (`BladeOne`). ### Discussion Both classes, `PhpCodeExtractor` and `BladeCodeExtractor` duplicate some code, `$options` and `$functionsScannerClass`: https://github.com/strarsis/i18n-command/blob/add-blade-extractor/src/PhpCodeExtractor.php#L13-L46 https://github.com/strarsis/i18n-command/blob/add-blade-extractor/src/BladeCodeExtractor.php#L13-L46 Side note: Putting these two aforementioned fields `$options` and `$functionsScannerClass` into a PHP `trait` doesn't work as PHP `trait`s can't override class fields (as I learned by trying to do so). Both classes have to extend from a class from `gettext/gettext`, therefore a trivial way for letting both classes share these fields doesn't seem to exist, so I think those duplications (which are quite compact) can be tolerated.

If there are still issues you can also install and use wp i18n from its current master until a new release is made: Add support for PHP-Blade files by strarsis · Pull Request #304 · wp-cli/i18n-command · GitHub

el_skak · July 8, 2022, 9:29pm

Hi Strasis
Thank you for your reply. I tried (maybe I did it wrong) to update i18n to ver. 2.3.0
Now I get this error when running yarn translate:

I ran this command to update
wp package install git@github.com:wp-cli/i18n-command.git
(I wasn’t sure what to do with the zip file from your link)

strarsis · July 8, 2022, 9:33pm

Yes, this happens with the current release of wp i18n, a fix was already merged, but no release yet:

github.com/wp-cli/i18n-command

`theme.json` not processed: `Theme stylesheet detected. PHP Warning: Invalid argument supplied for foreach()`

opened 07:14PM - 10 May 22 UTC

closed 05:38PM - 11 May 22 UTC

strarsis

state:unconfirmed command:i18n-make-pot

## Bug Report - [x] Yes, I reviewed the [contribution guidelines](https://make.…wordpress.org/cli/handbook/contributing/). - [x] Yes, more specifically, I reviewed the guidelines on [how to write clear bug reports](https://make.wordpress.org/cli/handbook/bug-reports/). **Describe the current, buggy behavior** The (valid) `theme.json` is not processed by `wp i18n`, no translation strings are extracted from it. A PHP warning occurs: ```` Theme stylesheet detected. PHP Warning: Invalid argument supplied for foreach() in phar:///usr/local/bin/wp/vendor/wp-cli/i18n-command/src/ThemeJsonExtractor.php on line 209 PHP Stack trace: PHP 1. {main}() /usr/local/bin/wp:0 PHP 2. include() /usr/local/bin/wp:4 PHP 3. include() phar:///usr/local/bin/wp/php/boot-phar.php:11 PHP 4. WP_CLI\bootstrap() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php:27 PHP 5. WP_CLI\Bootstrap\LaunchRunner->process($state = class WP_CLI\Bootstrap\BootstrapState { private $state = ['context_manager' => class WP_CLI\ContextManager { ... }] }) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php:78 PHP 6. WP_CLI\Runner->start() phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:28 PHP 7. WP_CLI\Runner->do_early_invoke($when = 'before_wp_load') phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1170 PHP 8. WP_CLI\Runner->run_command_and_exit($help_exit_warning = *uninitialized*) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:125 PHP 9. WP_CLI\Runner->run_command($args = [0 => 'i18n', 1 => 'make-pot', 2 => '.', 3 => './resources/lang/theme.pot'], $assoc_args = [], $options = *uninitialized*) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:440 PHP 10. WP_CLI\Dispatcher\Subcommand->invoke($args = [0 => '.', 1 => './resources/lang/theme.pot'], $assoc_args = [], $extra_args = []) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:417 PHP 11. call_user_func:{phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php:491}($function_name = class Closure { virtual $closure = "$this->WP_CLI\Dispatcher\{closure}", public $static = ['callable' => [...]]; public $parameter = ['$args' => '<required>', '$assoc_args' => '<required>'] }, ...$parameters = variadic([])) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php:491 PHP 12. WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure:phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:97-104}($args = [0 => '.', 1 => './resources/lang/theme.pot'], $assoc_args = []) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php:491 PHP 13. call_user_func:{phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:100}($function_name = [0 => class WP_CLI\I18n\MakePotCommand { protected $source = '/home/build/src/example.com/site/web/app/themes/theme'; protected $destination = './resources/lang/theme.pot'; protected $merge = [...]; protected $exceptions = [...]; protected $subtract_and_merge = NULL; protected $include = [...]; protected $exclude = [...]; protected $slug = 'theme'; protected $main_file_data = [...]; protected $skip_js = FALSE; protected $skip_php = FALSE; protected $skip_blade = FALSE; protected $skip_block_json = FALSE; protected $skip_theme_json = FALSE; protected $skip_audit = FALSE; protected $location = TRUE; protected $headers = [...]; protected $domain = 'theme'; protected $package_name = NULL; protected $file_comment = NULL; protected $project_type = 'theme' }, 1 => '__invoke'], ...$parameters = variadic([])) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:100 PHP 14. WP_CLI\I18n\MakePotCommand->__invoke($args = [0 => '.', 1 => './resources/lang/theme.pot'], $assoc_args = []) phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php:100 PHP 15. WP_CLI\I18n\MakePotCommand->extract_strings() /home/build/.wp-cli/packages/vendor/wp-cli/i18n-command/src/MakePotCommand.php:285 PHP 16. WP_CLI\I18n\ThemeJsonExtractor::fromDirectory($dir = '/home/build/src/example.com/site/web/app/themes/theme', $translations = class Gettext\Translations { protected $headers = ['Project-Id-Version' => 'Theme 1.0.0', 'Report-Msgid-Bugs-To' => 'https://wordpress.org/support/theme/theme', 'Last-Translator' => 'FULL NAME <EMAIL@ADDRESS>', 'Language-Team' => 'LANGUAGE <LL@li.org>', 'MIME-Version' => '1.0', 'Content-Type' => 'text/plain; charset=UTF-8', 'Content-Transfer-Encoding' => '8bit', 'POT-Creation-Date' => '2022-05-10T21:12:15+02:00', 'PO-Revision-Date' => 'YEAR-MO-DA HO:MI+ZONE', 'X-Generator' => 'WP-CLI 2.6.0', 'X-Domain' => 'theme']; protected $translationClass = 'Gettext\\Translation'; private ${ArrayObject}storage = ['Theme' => class Gettext\Translation { ... }, 'https://www.example.com' => class Gettext\Translation { ... }, 'Test theme.' => class Gettext\Translation { ... }, 'Author' => class Gettext\Translation { ... }, 'https://www.web-design-hosting.eu' => class Gettext\Translation { ... }] }, $options = ['restrictFileNames' => [0 => 'theme.json'], 'include' => [], 'exclude' => [0 => 'node_modules', 1 => '.git', 2 => '.svn', 3 => '.CVS', 4 => '.hg', 5 => 'vendor', 6 => 'Gruntfile.js', 7 => 'webpack.config.js', 8 => '*.min.js'], 'extensions' => [0 => 'json']]) /home/build/.wp-cli/packages/vendor/wp-cli/i18n-command/src/MakePotCommand.php:676 PHP 17. WP_CLI\I18n\ThemeJsonExtractor::fromFile($file_or_files = [0 => '/home/build/src/example.com/site/web/app/themes/theme/.budfiles/bud/modules.json', 1 => '/home/build/src/example.com/site/web/app/themes/theme/.budfiles/bud/profile.json', 2 => '/home/build/src/example.com/site/web/app/themes/theme/composer.json', 3 => '/home/build/src/example.com/site/web/app/themes/theme/jsconfig.json', 4 => '/home/build/src/example.com/site/web/app/themes/theme/package.json', 5 => '/home/build/src/example.com/site/web/app/themes/theme/public/app.3be68fa733011d85f572.hot-update.json', 6 => '/home/build/src/example.com/site/web/app/themes/theme/public/app.daf54ef2be6639ef729e.hot-update.json', 7 => '/home/build/src/example.com/site/web/app/themes/theme/public/editor.3be68fa733011d85f572.hot-update.json', 8 => '/home/build/src/example.com/site/web/app/themes/theme/public/editor.daf54ef2be6639ef729e.hot-update.json', 9 => '/home/build/src/example.com/site/web/app/themes/theme/public/entrypoints.json', 10 => '/home/build/src/example.com/site/web/app/themes/theme/public/hmr.json', 11 => '/home/build/src/example.com/site/web/app/themes/theme/public/manifest.json', 12 => '/home/build/src/example.com/site/web/app/themes/theme/theme.json'], $translations = class Gettext\Translations { protected $headers = ['Project-Id-Version' => 'Theme 1.0.0', 'Report-Msgid-Bugs-To' => 'https://wordpress.org/support/theme/theme', 'Last-Translator' => 'FULL NAME <EMAIL@ADDRESS>', 'Language-Team' => 'LANGUAGE <LL@li.org>', 'MIME-Version' => '1.0', 'Content-Type' => 'text/plain; charset=UTF-8', 'Content-Transfer-Encoding' => '8bit', 'POT-Creation-Date' => '2022-05-10T21:12:15+02:00', 'PO-Revision-Date' => 'YEAR-MO-DA HO:MI+ZONE', 'X-Generator' => 'WP-CLI 2.6.0', 'X-Domain' => 'theme']; protected $translationClass = 'Gettext\\Translation'; private ${ArrayObject}storage = ['Theme' => class Gettext\Translation { ... }, 'https://www.example.com' => class Gettext\Translation { ... }, 'Test theme.' => class Gettext\Translation { ... }, 'Author' => class Gettext\Translation { ... }, 'https://www.web-design-hosting.eu' => class Gettext\Translation { ... }] }, $options = ['restrictFileNames' => [0 => 'theme.json'], 'include' => [], 'exclude' => [0 => 'node_modules', 1 => '.git', 2 => '.svn', 3 => '.CVS', 4 => '.hg', 5 => 'vendor', 6 => 'Gruntfile.js', 7 => 'webpack.config.js', 8 => '*.min.js'], 'extensions' => [0 => 'json']]) phar:///usr/local/bin/wp/vendor/wp-cli/i18n-command/src/IterableCodeExtractor.php:97 PHP 18. WP_CLI\I18n\ThemeJsonExtractor::fromString($string = '\n{\n "$schema": "https://schemas.wp.org/trunk/theme.json",\n "version": 2,\n "settings": {\n "color": {\n "palette": [\n {\n "slug": "primary",\n "color": "#525ddc",\n "name": "Primary"\n }\n ],\n "custom": false,\n "customGradient": false,\n "defaultPalette": false,\n "defaultGradients": false\n },\n "custom": {\n "spacing": {},\n "typography": {\n "font-size": {},\n "line-height": {}\n }\n }', $translations = class Gettext\Translations { protected $headers = ['Project-Id-Version' => 'Theme 1.0.0', 'Report-Msgid-Bugs-To' => 'https://wordpress.org/support/theme/theme', 'Last-Translator' => 'FULL NAME <EMAIL@ADDRESS>', 'Language-Team' => 'LANGUAGE <LL@li.org>', 'MIME-Version' => '1.0', 'Content-Type' => 'text/plain; charset=UTF-8', 'Content-Transfer-Encoding' => '8bit', 'POT-Creation-Date' => '2022-05-10T21:12:15+02:00', 'PO-Revision-Date' => 'YEAR-MO-DA HO:MI+ZONE', 'X-Generator' => 'WP-CLI 2.6.0', 'X-Domain' => 'theme']; protected $translationClass = 'Gettext\\Translation'; private ${ArrayObject}storage = ['Theme' => class Gettext\Translation { ... }, 'https://www.example.com' => class Gettext\Translation { ... }, 'Test theme.' => class Gettext\Translation { ... }, 'Author' => class Gettext\Translation { ... }, 'https://www.web-design-hosting.eu' => class Gettext\Translation { ... }] }, $options = ['restrictFileNames' => [0 => 'theme.json'], 'include' => [], 'exclude' => [0 => 'node_modules', 1 => '.git', 2 => '.svn', 3 => '.CVS', 4 => '.hg', 5 => 'vendor', 6 => 'Gruntfile.js', 7 => 'webpack.config.js', 8 => '*.min.js'], 'extensions' => [0 => 'json'], 'file' => 'theme.json']) phar:///usr/local/bin/wp/vendor/wp-cli/i18n-command/src/IterableCodeExtractor.php:68 PHP 19. WP_CLI\I18n\ThemeJsonExtractor::get_fields_to_translate() phar:///usr/local/bin/wp/vendor/wp-cli/i18n-command/src/ThemeJsonExtractor.php:43 PHP 20. WP_CLI\I18n\ThemeJsonExtractor::extract_paths_to_translate($i18n_partial = ['title' => 'Style variation name', 'settings' => ['typography' => [...], 'color' => [...], 'blocks' => [...]], 'customTemplates' => [0 => [...]], 'templateParts' => [0 => [...]]], $current_path = *uninitialized*) phar:///usr/local/bin/wp/vendor/wp-cli/i18n-command/src/ThemeJsonExtractor.php:166 PHP 21. WP_CLI\I18n\ThemeJsonExtractor::extract_paths_to_translate($i18n_partial = 'Style variation name', $current_path = [0 => 'title']) phar:///usr/local/bin/wp/vendor/wp-cli/i18n-command/src/ThemeJsonExtractor.php:222 Success: POT file successfully generated! ```` (Valid )`theme.json` that causes the issue: ```json { "$schema": "https://schemas.wp.org/trunk/theme.json", "version": 2, "settings": { "color": { "palette": [ { "slug": "primary", "color": "#525ddc", "name": "Primary" } ], "custom": false, "customGradient": false, "defaultPalette": false, "defaultGradients": false }, "custom": { "spacing": {}, "typography": { "font-size": {}, "line-height": {} } }, "spacing": { "padding": true, "units": ["px", "%", "em", "rem", "vw", "vh"] }, "typography": { "customFontSize": false } } } ```` **Describe how other contributors can replicate this bug** - Use a theme that contains this (valid )`theme.json`: ```json { "$schema": "https://schemas.wp.org/trunk/theme.json", "version": 2, "settings": { "color": { "palette": [ { "slug": "primary", "color": "#525ddc", "name": "Primary" } ], "custom": false, "customGradient": false, "defaultPalette": false, "defaultGradients": false }, "custom": { "spacing": {}, "typography": { "font-size": {}, "line-height": {} } }, "spacing": { "padding": true, "units": ["px", "%", "em", "rem", "vw", "vh"] }, "typography": { "customFontSize": false } } } ```` - Invoke `wp i18n` inside the theme directory: `wp i18n make-pot . ./resources/lang/theme.pot` Notice the PHP warning and that translation strings in `theme.json` are not extracted. **Describe what you would expect as the correct outcome** No PHP warning and translation strings extracted from `theme.json`. **Let us know what environment you are running this on** ``` OS: Linux 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 Shell: /bin/bash PHP binary: /usr/bin/php7.4 PHP version: 7.4.29 php.ini used: /etc/php/7.4/cli/php.ini MySQL binary: /usr/bin/mysql MySQL version: mysql Ver 8.0.29-0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu)) SQL modes: WP-CLI root dir: phar://wp-cli.phar/vendor/wp-cli/wp-cli WP-CLI vendor dir: phar://wp-cli.phar/vendor WP_CLI phar path: /home/build/src/[...]/[...]/test-theme WP-CLI packages dir: /home/build/.wp-cli/packages/ WP-CLI global config: WP-CLI project config: /home/build/src/[...]/site/wp-cli.yml WP-CLI version: 2.6.0 ``` **Provide a possible solution** Probably some mismatch of expected `theme.json` data structure and extractor logic that needs to be fixed.

You can install and use wp i18n from source directly to use that fix.
You would then invoke wp i18n using the path to the cloned directory.

strarsis · July 8, 2022, 9:44pm

Addendum: It turns out that when using --include with wp i18n the theme.json has to be explicitly included, too:

github.com/roots/sage

Include `theme.json` in translation scan command

roots:main ← strarsis:add-themejson-i18n-cmd

opened 09:36PM - 08 Jul 22 UTC

strarsis

+1 -1

It turns out that when using `--include` with `wp i18n` the `theme.json` [needs …to be explicitly included, too](https://github.com/wp-cli/i18n-command/issues/322#issuecomment-1124063949), as it would be skipped otherwise. The merging of this PR IMHO should be postponed until a new release of `wp i18n` as including the `theme.json` causes an issue with the current `wp i18n` release: https://github.com/wp-cli/i18n-command/issues/322#issuecomment-1155692969 As a workaround the current source of `wp i18n` must be used instead.

This change will make wp i18n use the theme.json, but also trigger an issue with current wp i18n release (theme.json iteration bug), so you should use the current source.

el_skak · July 8, 2022, 9:45pm

OK. Thank you. I will try again tomorrow. It is almost midnight here now. Thanks again

el_skak · July 9, 2022, 2:10pm

So, I’ve tried spending some time on this today. I think its very difficult for me to make it work.
I’ve triede to find out whick version of i18n I am using. I think I’ve managed to downgrade my version by manually deleting the contets of this folder ~ /Users/bo/.wp-cli/packages/vendor/wp-cli/i18n-command
I have also tried to uninstall wp-cli and I have added “theme.json” to my translate script

    "translate:pot": "wp i18n make-pot . ./resources/lang/sage.pot --include=\"app,resources,./theme.json\"",

So now I just get this error - which is the same I got before to begin with:

And when I try to upgrade i18n (wp package install git@github.com:wp-cli/i18n-command.git) I’m back to this error:

How do I know the version of my current i18n? Can’t I just delete everything and get a clean install of wp cli and then add “theme.json” to my --include list

strarsis · July 9, 2022, 4:53pm

@el_skak: This is how I use it with wp i18n from source (with all the yet to be released bug fixes included):

(cwd into ~/src)
git clone https://github.com/wp-cli/i18n-command
(cwd into ~/src/i18n-command)
composer install to install the wp i18n dependencies.

Sage theme package.json:

    "translate": "yarn translate:pot && yarn translate:update",
    "translate:pot": "~/src/i18n-command/vendor/bin/wp i18n make-pot . ./resources/lang/sage.pot --include=\"theme.json,app,resources\"",
    "translate:update": "for filename in ./resources/lang/*.po; do msgmerge -U $filename ./resources/lang/sage.pot; done; rm -f ./resources/lang/*.po~",
    "translate:compile": "yarn translate:mo && yarn translate:js",
    "translate:js": "~/src/i18n-command/vendor/bin/wp i18n make-json ./resources/lang --pretty-print",
    "translate:mo": "~/src/i18n-command/vendor/bin/wp i18n make-mo ./resources/lang ./resources/lang"

(Don’t forget to change the sage.pot back to the theme name/slug/domain, if you prefer and did that).
There are other ways of course, but this is the simplest and least intrusive way IMHO.

I hope there will be a new release of wp i18n soon, as it also contains a new merge command that allows getting rid of the shell script of translate:update.

el_skak · July 10, 2022, 9:17pm

Holy cow. It worked… After some head scratching
I only kept on trying to solve this because you have been so helpful. Otherwise, I would probably have given up.

First, I got an error saying that wp-cli was missing a file to translate. Then I deleted WP-cli completely
I used this guide:

On top of that, I deleted the ~/.wp-cli-folder.

And then I ran the yarn translate command. And it worked…
I still get an error from the translate:update command. But that is only until you have created your .po and .mo files.

I also added this to setup.php in the sage-theme so that WP knows where to find the language-files.

// Load language files
add_action('after_setup_theme', function () {
    load_theme_textdomain('sage', get_template_directory() . '/resources/lang');
});

Thanks a lot for your help, @strasis

strarsis · July 10, 2022, 10:07pm

You are welcome. Most issues should be fixed when the next wp i18n release is out.

Yes, this is because a shell script is used for merging the PO files with the newly generated POT files, it doesn’t check for non-existing PO files, but the error can be just ignored.
As mentioned in the previous post, the next release of wp i18n also has a merge command, so this shell script isn’t necessary anymore and no errors will then appear when there are no PO files yet.

el_skak · July 11, 2022, 9:14am

I will bookmark this thread until next time I need to translate my theme. That’s for sure. Thanks again.

strarsis · July 11, 2022, 10:56am

The translation docs need updating (was already mentioned in one of the package.json PRs), I should add some notes about the usage (when the new wp i18n version releases probably).

strarsis · July 11, 2022, 11:34am

@el_skak: As you are developing a multilingual WordPress site, you will probably also be interested in managing the core/plugins/themes languages. When you are also using Trellis, this guide may be interesting:

strarsis · July 18, 2022, 12:16pm

Update: wp i18n released a new version that addresses all these issues and also includes a command that updates PO files from POT files (merge). This is great news as this eliminates all external tools and shell-scripts for handling translation (gettext/json). Now wp itself also needs a new release so the bundled wp i18n is the latest one.

In the meantime, the latest release of wp i18n, regardless of current wp CLI version can be installed using
wp package install wp-cli/i18n-command:dev-main
(thanks @swissspidy (GitHub)) and then used as usual (wp i18n)

el_skak · July 19, 2022, 8:50am

Thanks, @strarsis. You have been very helpfull. I will bookmark this thread