This repository was archived by the owner on Jan 23, 2026. It is now read-only.
Use offical WP-CLI i18n package to generate POT file.#88
Open
Use offical WP-CLI i18n package to generate POT file.#88
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a composer script to generate POT files.
Technical Details
Utilize the wp-cli/i18n-command tool for the generation of POT files, as it is the official tool capable of translating both PHP and JS files. Given that Gutenberg introduced localization functions in JS files, this tool ensures comprehensive coverage.
The generation process will result in the creation of a POT file within the
languagesdirectory.Abstain from creating a GitHub action workflow for POT file generation due to the resource-intensive nature of the task, involving both high memory and CPU usage. This complexity can lead to potential failures within the GitHub action workflow.
Commands
composer run potto generate POT files.npm run potto generate POT file. It's an alias tocomposer run pot.How to test
npm installto install JS packages.composer updateto install PHP packages.npm run initto initialize the plugin.composer run potto generate POT file.Fixes/Covers issue
Fixes #87
Reference
https://github.com/rtCamp/features-plugin-skeleton/pull/482