I've done some research and found that django translations don't show up when a string is marked as "fuzzy".
However, I haven't been able to find any documentation on whether I can override this behaviour.
Is there a Django setting that can be used to allow Django (or gettext) to use "fuzzy translations"?
I know a lot of the automated translations won't be perfect, but this is for demonstration, development and testing for an open-source product.
I'd rather have users be able to develop in their own language with "approximate" translations then use that as an incentive to check them off as they go.
1 Answers
Answers 1
It would be unfortunate to show these translations as some of them are most certainly wrong. You are supposed to remove the fuzzy tag when you update the translations and revise the guessed translations that are marked as fuzzy.
However, you may run a tool to quickly delete the fuzzy markers from a .po file: Removing all fuzzy entries of a PO file
UPDATE
Here is a great overview of the GNU gettext work-flow: https://www.gnu.org/software/gettext/manual/gettext.html#Overview
It is msgfmt that strips the fuzzy translations. It has an option --use-fuzzy that includes the fuzzy translations.
msgfmt is wrapped by compilemessages django admin command, which since version 1.8 has the --use-fuzzy option too (https://docs.djangoproject.com/en/1.9/ref/django-admin/#compilemessages)
0 comments:
Post a Comment