Opened 12 years ago

Closed 9 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 Claude Paroz, 12 years ago

Triage Stage: Unreviewed → Accepted

comment:2 by Ramiro Morales, 11 years ago

Resolution: → duplicate
Status: new → closed

Duplicate of #10852.

comment:3 by Ramiro Morales, 11 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 Anton Baklanov, 11 years ago

Cc: antonbaklanov@… added
Owner: changed from nobody to Anton Baklanov
Status: new → assigned
Version: 1.4 → master

comment:5 by Anton Baklanov, 11 years ago

Has patch: set

​pull request

comment:6 by Tim Graham, 10 years ago

Patch needs improvement: set

Patch no longer merges cleanly.

comment:7 by Anton Baklanov, 10 years ago

Patch needs improvement: unset

​new, rebased pull request

comment:8 by flagZ, 10 years ago

I could really use this. Any ETA on inclusion?

comment:9 by Tim Graham, 10 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:10 by Claude Paroz <claude@…>, 10 years ago

In 3a435a057c691bf9d5936766f54c5f9bd01be176:

Set compile messages options as class variable

Refs #18714. Same logic as options for makemessages commands.

comment:11 by Claude Paroz <claude@…>, 10 years ago

In 0424c84d541d7b0e23783c33c2db495543e3bd47:

[1.7.x] Set compile messages options as class variable

Refs #18714. Same logic as options for makemessages commands.
Backport of 3a435a057 from master.

comment:12 by Claude Paroz, 10 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 Anton Baklanov, 10 years ago

Has patch: unset
Patch needs improvement: unset

working on adapting patch to current master state

comment:14 by Anton Baklanov, 9 years ago

Has patch: set

​new pull request

comment:15 by Berker Peksag, 9 years ago

Triage Stage: Accepted → Ready for checkin

​PR #3553 LGTM. I've reviewed and tested the patch locally.

comment:16 by Claude Paroz <claude@…>, 9 years ago

Resolution: → fixed
Status: assigned → closed

In d63703f1cd373f2a1d52e1947835b44d9565c1e0:

Fixed #18714 -- Added 'fuzzy' compilemessages option

Note: See TracTickets for help on using tickets.
Back to Top