“Post Tags” string (on admin menu and in Post Tags metabox) not translatable

[demetris]

I’m seeing this on r10845 with the latest wordpress.pot.

Demetris

[hakre]

If it is a new string, then the translation teams need to get some time to translate it first. As long as there is no translation available, the default string will be displayed.

Which language are you using?

[demetris]

hakre, the ticket says that the string is not translat*able*, not that it is not tranlat*ed*.

To be more exact, and to provide some information I should have provided when I opened the ticket, there *is* a “Post Tags” string in the trunk wordpress.pot, I translated it, but I keep seeing the original string.

[nbachiyski]

The problem is that the default taxonomies are created before the translations are loaded. Here is a patch, which moves the creation on init.

[ryan]

(In [10965]) Create default taxonomies upon init. Props nbachiyski. fixes #9399

This adds additional test combinations to the workflow that tests the build process that run on Node.js versions 22 and 24.

22.x is the Active LTS version for Node.JS and scheduled to become Maintenance LTS in October when 24.x graduates to the Active LTS. Testing against these versions will help spot any potential compatibility issues that come up and can make upgrading in the future.

This pull request tests both the Gutenberg and Core build processes with these versions. This is an alternate approach to #9399.

This results in 24 additional jobs in the test matrix. These new jobs will only run within wordpress-develp, not within forks.

Trac ticket: