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

Put the language MO files inside this repository (?) #4801

Open
jnm opened this issue Jan 10, 2024 · 0 comments
Open

Put the language MO files inside this repository (?) #4801

jnm opened this issue Jan 10, 2024 · 0 comments
Labels

Comments

@jnm
Copy link
Member

jnm commented Jan 10, 2024

Django itself stores .mo files in git. We could do that too and get rid of compilemessages as a build step.

Originally posted by @jnm in #3820 (comment)

Further thought 1) compilemessages has lead to some "why does my build not work today" issues seen on internal chat when something is wrong with translations. I'd rather see this done in a CI bot or manually on some schedule. Storing the mo file in git is fine. It's storing a snapshot of the translations at a point in time. Maybe it's not perfectly normalized as it's really a computed value, but it's good enough and the mo files do have unique meaning in that they are known to be working translations.

Originally posted by @bufke in #3820 (comment)

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

No branches or pull requests

1 participant