search

txty-io / texterify

The translation and localization management system.
https://texterify.com
Other
175 stars 14 forks source link

WordPress / `.pot` support #59

Closed matzeeable closed 2 years ago

matzeeable commented 3 years ago

Hey Texterify team!

Your solution looks really promising, and we are currently investigating to automate our localization extraction, versioning and management to get a complete continuous localization system.

That is what we have achieved so far:

  1. We push changes to our WordPress plugin via GIT
  2. Our CI enters the job build plugin
  3. We extract language / i18n keys from source files to a .pot file
  4. We push the .pot file to a translation management tool, so we can translate it (this part is missing)
  5. We pull the .po files from the translation management tool (this part is missing)
  6. The plugin is built with language files

We want to avoid holding any translation data in our GIT repository.

Step 4 and 5 is prepared in our CI, so we can introduce a simple CLI call that fits the needs.

Is this something Texterify can be used for?

Regards Matthew 😊

chrztoph commented 3 years ago

Hi Matthew, 👋

do you also want to push your existing keys during build in your CI to Texterify or just your new keys? Because this is something we haven't thought of. Most people I know are pulling the latest translations in their CI, but do not also upload them. This is done during development by the developers. Uploading new keys sounds like an awesome idea, but for already existing keys I think this could introduce some issues. How do you want to work with Texterify? We will definitely find a way that works for you. 🙂

Downloading your translations is super easy. Install the Texterify CLI (https://github.com/texterify/texterify-cli) and then use the command texterify download to download all your translations. If you need help with that let me know.

chrztoph commented 2 years ago

Closed in favor of #61.