# Stop Django from creating fuzzy entries

**URL:** <https://forum.djangoproject.com/t/stop-django-from-creating-fuzzy-entries/31518>\
**Category:** Internationalization\
**Created:** [May 26, 2024, 7:41am UTC](https://forum.djangoproject.com/t/stop-django-from-creating-fuzzy-entries/31518 "2024-05-26T07:41:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![OmidShojaee](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/omidshojaee/32/2216_2.png) [@OmidShojaee](https://forum.djangoproject.com/u/OmidShojaee)\
**Post date:** [May 26, 2024, 7:41am UTC](https://forum.djangoproject.com/t/stop-django-from-creating-fuzzy-entries/31518/1 "2024-05-26T07:41:11Z")

</div>

Hello,  
I’m translating Django into my language and it creates some fuzzy entries in the .po file.

One of them is `Permissions` from `django.contrib.auth` and the other one is `Permission denied` from a library I’ve installed.

I know this happens when Django thinks those two entries are similar, but in this case they have a completely different meaning and purpose. Also, none of them are from my own apps.

Is there a way to stop `makemessages` command to create fuzzy entries?

---

<div class="post-metadata">

**Author:** ![claudep](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/claudep/32/5377_2.png) [@claudep](https://forum.djangoproject.com/u/claudep)\
**Post date:** [May 26, 2024, 3:28pm UTC](https://forum.djangoproject.com/t/stop-django-from-creating-fuzzy-entries/31518/2 "2024-05-26T15:28:41Z")

</div>

There is a won’t fix ticket for Django here where you can read some rationales behind the decision:

[https://code.djangoproject.com/ticket/10852](https://code.djangoproject.com/ticket/10852)

---

<div class="post-metadata">

**Author:** ![evnp](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/evnp/32/30979_2.png) [@evnp](https://forum.djangoproject.com/u/evnp)\
**Post date:** [December 19, 2025, 3:15pm UTC](https://forum.djangoproject.com/t/stop-django-from-creating-fuzzy-entries/31518/3 "2025-12-19T15:15:43Z")

</div>

We’re using an automated translation pipeline where some amount of “extra” translation is preferable over manual resolution of fuzzy entries. Thus, we’re very interested in this topic – appreciate the question and response as it led me to a workable solution.

Per discussion in [https://code.djangoproject.com/ticket/10852](https://code.djangoproject.com/ticket/10852) (linked by @claudep), it’s now possible to subclass the makemessages command and add an additional option for disabling “fuzzy entries” entirely. Add a file called `commands/makemessages.py` in any Django INSTALLED\_APP which has content along these lines:

```python
from django.core.management.commands import makemessages

class Command(makemessages.Command):
    msgmerge_options = makemessages.Command.msgmerge_options + ["--no-fuzzy-matching"]

```

Knowing this would have saved me some time/digging, paying it forward for anyone else coming across this.