Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WP Loco Translate workflow #11

Open
2 tasks
yannlugrin opened this issue Sep 30, 2021 · 0 comments
Open
2 tasks

WP Loco Translate workflow #11

yannlugrin opened this issue Sep 30, 2021 · 0 comments

Comments

@yannlugrin
Copy link
Member

💬 Describe the task

To ease both development and deploy, we need to refactor how we use and deploy translation strings.

Here is how it should work:

  1. Locally, we can sync our translations to get new keys from the twig templates
  2. Then during deploy, we can generate .mo (impossible to version) and .pot (that disable template sync)
  3. Finally, admin can update string translations without being overridden during next deploy

Related to antistatique/holdibat#107

✅ Todo

Steps to achieve the task:

  • During deploy execute with gettext installed:
$ msgfmt source.po -o destination.mo # not sure if it's necessary regarding the next step
$ msgfilter -i fr_FR.po -o holdibat.pot true
  • Then still during deploy, remove all the commited .po to favour the string in the database

🧞 Expected result

Good DX and DB-first string translations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant