#10852: Add no-fuzzy-matching option to makemessages
-------------------------------------+-------------------------------------
Reporter: graham.carlyle@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by claudep):
It's not ridiculous, it's fuzzy matching. It helps the translator ~80% of
the time, and ~20% of the time it's completely wrong. But it doesn't
matter that much because fuzzy strings are not included in compiled
messages. So it's the translator's work to evaluate accuracy of the fuzzy
proposal, and simply dismiss it when it does not make sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/10852#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/087.dbe3a9726a9fc300465322848a8a5b42%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
