#23321: Remove .mo files from the Django Git repository
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Hello everyone!
As a Django release manager, and as someone who went thru the super
painful process of incorporating translations from Transifex into Django
5.0, I'd like to express a big +1 to remove the .mo files from the Django
source. I agree with Ningú's counterpoints to Jannis Leidel's comment:7,
and also I'd like to add:
* Automatic compiling .po files when running tests would not add
noticeable overhead since we could add a flag to use the existing ones if
available (like `keep-db`, perhaps `on` by default)
* Manually compiling .po files when developing Django and/or a from-repo
version of Django *and* working on i18n related issues, feels natural to
me (as long as we properly document this)
* I haven't used Babel before but even assuming that this is a superior
lib, I think that that migration should be treated and pushed forward as
an orthogonal issue and not block improvements to our current (sometimes
painful) translations machinery.
Claude, question: in your PR, why are you favoring using `msgfmt` directly
instead of using the Django `compilemessages` command (perhaps its
internal `compile_messages` helper)?
--
Ticket URL: <https://code.djangoproject.com/ticket/23321#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cd63d5bd0-b8fec5f1-2340-48fb-887a-bb151bb691e6-000000%40eu-central-1.amazonses.com.
