[Django] #28279: Feature - Stable output for the makemessages command

[Django]

#28279: Feature - Stable output for the makemessages command
-------------------------------------+-------------------------------------
Reporter: Pierre | Owner: nobody
Sassoulas |
Type: | Status: new
Cleanup/optimization |
Component: Core | Version: 1.11
(Management commands) | Keywords: makemessages stable
Severity: Normal | vcs
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I'm using a VCS to track my i18n directory, and very often after changing
one or two strings, the content change elsewhere after launching "python
manage.py makemessages".

For example :

{{{
-" lorem ipsum etc.\n"
+" lorem ipsum "
+"etc.\n"
}}}

Or :

{{{
-msgstr ""
-"Django, Le framework web pour les perfectionnistes ayant des échéances"
+msgstr "Django, Le framework web pour les perfectionnistes ayant des
échéances"
}}}

It makes merge and rebase a lot more complicated, because it prevent them
to be done automatically by the VCS.

Would it be feasible to have some fixed format that would make the locale
directory more stable ?

--
Ticket URL: <https://code.djangoproject.com/ticket/28279>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#28279: Feature - Stable output for the makemessages command
-------------------------------------+-------------------------------------

Reporter: Pierre Sassoulas | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Management | Version: 1.11
commands) |
Severity: Normal | Resolution: invalid
Keywords: makemessages stable | Triage Stage:
vcs | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Claude Paroz):

* status: new => closed
* resolution: => invalid

Comment:

You are talking about the `--no-wrap` option of many gettext tools. Django
also offers the same option with the `makemessages` command.
If your .po files are transiting through some translation tool or
platform, it may happen that one of these is using `--no-wrap`, hence the
formatting difference.
I don't see what Django can do for this. It's up to you to set your
wrapping policy and enforce it throughout your translation toolchain.

--
Ticket URL: <https://code.djangoproject.com/ticket/28279#comment:1>