[Django] #31690: Document how fuzzy strings are handled by compilemessages
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: 3.0
Documentation | Keywords: translation i18n
Severity: Normal | fuzzy compilemessages makemessages
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
I would like to add a passage about how fuzzy strings are handled by the
compilemessages command here:
https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#miscellaneous
I'm pretty new to gettext and didn't know about the concept of fuzzy
translations. I overlooked / ignored the fuzzy statements, which were
automatically generated by invoking makemessages. It cost me quite some
time today to figure out why those translations did not work and I think
this may have been prevented by some documentation about it.
I hereby want to reassure that this is a feasible thing to add.
--
Ticket URL: <https://code.djangoproject.com/ticket/31690>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Severity: Normal | Resolution:
Keywords: translation i18n | Triage Stage:
fuzzy compilemessages | Unreviewed
makemessages |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
I'm not sure we should explain `gettext` functionality in Django docs. The
`use_fuzzy` option in https://docs.djangoproject.com/en/stable/ref/django-
admin/#django-admin-compilemessages should be a good hint to check if
something doesn't work the way you think.
Maybe linking to https://www.gnu.org/software/gettext/manual/html_node
/Fuzzy-Entries.html in the `use_fuzzy` explanation?
--
Ticket URL: <https://code.djangoproject.com/ticket/31690#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Severity: Normal | Resolution:
Keywords: translation i18n | Triage Stage:
fuzzy compilemessages | Unreviewed
makemessages |
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by sebashwa):
Replying to [comment:1 Claude Paroz]:
> I'm not sure we should explain `gettext` functionality in Django docs.
The `use_fuzzy` option in https://docs.djangoproject.com/en/stable/ref
/django-admin/#django-admin-compilemessages should be a good hint to check
if something doesn't work the way you think.
> Maybe linking to https://www.gnu.org/software/gettext/manual/html_node
/Fuzzy-Entries.html in the `use_fuzzy` explanation?
I agree that this should rather be a short hint and not a fully fledged
explanation. But I especially would like to mention the fact somewhere in
the django docs, that those fuzzy translations are automatically generated
by makemessages sometimes. So maybe a small hint box here:
https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#message-
files stating that this can happen (and maybe when it happens) is the way
to go? Including the link to the docs at gnu.org you are mentioning would
work fine here as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/31690#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: sebashwa
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: 3.0
Severity: Normal | Resolution:
fuzzy compilemessages | checkin
makemessages |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
* owner: nobody => sebashwa
* status: new => assigned
* has_patch: 0 => 1
* stage: Accepted => Ready for checkin
Comment:
[https://github.com/django/django/pull/13053 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/31690#comment:4>
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: sebashwa
Cleanup/optimization |
Component: Documentation | Version: 3.0
Keywords: translation i18n | Triage Stage: Ready for
fuzzy compilemessages | checkin
makemessages |
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"3d664a158de18acf72fc8e0671f0f390cbca4b2e" 3d664a1]:
{{{
#!CommitTicketReference repository=""
revision="3d664a158de18acf72fc8e0671f0f390cbca4b2e"
Fixed #31690 -- Added note about fuzzy entries in translation docs.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31690#comment:5>
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: sebashwa
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.0
Severity: Normal | Resolution: fixed
Keywords: translation i18n | Triage Stage: Ready for
fuzzy compilemessages | checkin
makemessages |
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"2d3b6bce28148fb0b8cf0939098bb6fe03d1b4f5" 2d3b6bce]:
{{{
#!CommitTicketReference repository=""
revision="2d3b6bce28148fb0b8cf0939098bb6fe03d1b4f5"
[3.1.x] Fixed #31690 -- Added note about fuzzy entries in translation
docs.
Backport of 3d664a158de18acf72fc8e0671f0f390cbca4b2e from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31690#comment:6>
Django
-------------------------------------+-------------------------------------
Reporter: sebashwa | Owner: sebashwa
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.0
Severity: Normal | Resolution: fixed
Keywords: translation i18n | Triage Stage: Ready for
fuzzy compilemessages | checkin
makemessages |
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"33767d5ab6d6642b324b180a308e62312bd6c685" 33767d5a]:
{{{
#!CommitTicketReference repository=""
revision="33767d5ab6d6642b324b180a308e62312bd6c685"
[3.0.x] Fixed #31690 -- Added note about fuzzy entries in translation
docs.
Backport of 3d664a158de18acf72fc8e0671f0f390cbca4b2e from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31690#comment:7>