Opened 12 years ago
Closed 10 years ago
#18714 closed New feature (fixed)
Add an option to compilemessages to compile fuzzy translations
Reported by: | rasca | Owned by: | Anton Baklanov |
---|---|---|---|
Component: | Core (Management commands) | Version: | dev |
Severity: | Normal | Keywords: | compilemessages fuzzy msgfmt |
Cc: | rasca7@…, antonbaklanov@… | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
msgfmt
has an option to compile fuzzy messages: -f
or --use-fuzzy
. I propose adding this parameter to the compilemessages command.
It would be useful in a project I'm working on where we code in English but the client reviews it in Spanish and we translate the messages for a development deployment (leaving them fuzzy) and once we are ready for shipping a translator checks all the fuzzy messages.
Without this option either the develop deployment stays untranslated or the translator doesn't know which strings are the new ones that he has to check.
Change History (16)
comment:1 by , 12 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 12 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:3 by , 12 years ago
Resolution: | duplicate |
---|---|
Status: | closed → new |
Sorry, it seems I'm unable to read today. #10852 was about makemessages and this one is about compilemessages.
comment:4 by , 12 years ago
Cc: | added |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Version: | 1.4 → master |
comment:9 by , 11 years ago
Patch needs improvement: | set |
---|
@flagZ, can you review the patch? It needs to be updated since 1.7 is now feature frozen.
comment:12 by , 11 years ago
I've just committed a slight improvement (simple enough to warrant 1.7 backport), which allows someone to subclass the command to add complementary options with one line of code (in the same vein as 06efeae598c6dafbe56d2ea323a0dccdd5bf2b8e).
But the patch still makes sense (to be able to specify --fuzzy per command invocation).
comment:13 by , 10 years ago
Has patch: | unset |
---|---|
Patch needs improvement: | unset |
working on adapting patch to current master state
comment:15 by , 10 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
PR #3553 LGTM. I've reviewed and tested the patch locally.
comment:16 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Duplicate of #10852.