#10852: Add no-fuzzy-matching option to makemessages
----------------------------------------------------+-----------------------
Reporter: graham.carl...@maplecroft.com | Owner: nobody
Status: closed | Milestone:
Component: Internationalization | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------------+-----------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Okay, this is a non-issue. As Ramiro points out, the fuzzy annotation
prevents the string from being used as a translation. 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.
Particularly in crowd-sourced translations, where multiple people are
going to be working on the same file, that's a huge win. In single-sourced
cases, it's never going to be a hinderance, either, once people understand
what fuzzy means.
So, no, we're not going to provide an option not to include those. They're
normal parts of GNU PO files and experienced translators expect them, are
used to working with them and gain benefit from them. Less experienced
translators become more experienced as time goes by.
--
Ticket URL: <http://code.djangoproject.com/ticket/10852#comment:4>
Django <http://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
-~----------~----~----~----~------~----~------~--~---
