#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 internaut):
I stumbled upon this discussion because "fuzzy" entries in the PO files
caused big problems for me, too. I mean, "fuzzy" is ''way'' to fuzzy in
makemessages. Some examples: The string "has geolocation" gets a fuzzy
match to the string "Translation". "Further description" is believed to be
the same as "Add an inscription". "edit" is supposed to be the same as
"edition". It's just ridiculous. Because Django doesn't have a "non-fuzzy"
option for makemessages, I ended up hacking
''./core/management/commands/makemessages.py'' and adding ''-N'' to the
list of msgmerge arguments on line 197. I honestly don't understand why no
option to disable fuzzy matching is added to makemessages.
--
Ticket URL: <https://code.djangoproject.com/ticket/10852#comment:12>
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.621c5a4415d0c1b65bb52d4bf75bcf91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
