#10852: Add no-fuzzy-matching option to makemessages
-------------------------------------+-------------------------------------
Reporter: graham.carlyle@… | Owner: nobody
Type: Uncategorized | Status: reopened
Component: | Version: SVN
Internationalization | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by justinkhill@…):
* status: closed => reopened
* resolution: wontfix =>
Comment:
Replying to [comment:5 EmilStenstrom]:
> Replying to [comment:4 mtredinnick]:
> > "However, it should be kept in the PO file because it saves
translators work, particularly in the update phase, as they can see what a
likely match is going to be"
>
> I've seen many instances where translators are confused by the "almost
correct" versions of strings, and instead miss them entirely. We've had
greater success when manually going through the translation files and
removing all the fuzzy strings entirely. For this reason, I'm strongly in
favour of a flag for disabling fuzzy strings.
I second that. Our translator actually asked me to disable fuzzy, saying
"django probably has a way to turn that off". He didn't elaborate, but
said fuzzy has caused havoc for them in the past on other projects. Since
this isn't an option, I'll be removing the fuzzy translations manually,
before sending them off.
--
Ticket URL: <https://code.djangoproject.com/ticket/10852#comment:6>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
