> Also, what does 'fuzzy' mean in my .po file?
I'm not an authority on the subject but have dealt with translations
and .po files quite a bit.
The term "fuzzy" in this context means it's not an EXACT match, but
it's very similar; i.e. a "fuzzy match".
The "fuzzy" usually shows up when the original text (in the template
marked with {%trans/blocktrans%} or in the code marked with
ugettext_lazy/_()) has been MODIFIED slightly since the translations
were first written.
It can also show up when a new piece of text appears in the original
text, which doesn't have its own translation yet, but is a pretty
close match for another piece of text that DOES have a translation.
It's *very important* that you find and evaluate them, because the
"fuzzy" matcher isn't too smart; "don't start a fire" and "go start a
fire" would probably count as a fuzzy match even though they
ultimately mean the opposite thing, for example. If the fuzzy matcher
got lucky and it's a good match, manually remove the ", fuzzy" from
the comment in the .po. If it was wrong, fix the translation and
remove the ", fuzzy" from the comment in the .po.
(I didn't find documentation for this back when I first started using
it, so those are just my unofficial instructions derived through
trial&error).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
