"django.contrib.humanize" Turkish Translation Error

[ruless@…]

When I use "naturaltime" templatetag with the datetimefield value it translates as "{u'count': 2} saat önce" whereas it should be "2 saat önce" so there's a problem with translation numerical values.

Here are my codes;

#settings.py
LANGUAGE_CODE = 'tr'
DJANGO_APPS = (
'django.contrib.humanize'
)

#models.py
pub_date = models.DateTimeField("Yayınlanma Tarihi", auto_now_add=True)

#views.py
def show_article(request, slug):

article = Article.objects.get(slug=slug)
return render(request, 'news/show_article.html', {'article': article})

#template.html
{{ article.pub_date|naturaltime }}

I'm a pretty new Django user but after discussing this issue with some experienced users on #django channel, they've told me to open a ticket about it. I hope this information is enough.

[Claude Paroz]

You are right, the Turkish translation po file for contrib.humanize contains syntax errors and does not pass msgfmt -vc.

I've checked that the 2 offending strings are fixed in Transifex (we are safe for 1.6).

I'll update some of our scripts to not allow po files with errors. I will also backport the translation fix for 1.5, as it's a syntax error, not only a bad translation.

[Claude Paroz <claude@…>]

In 63b2155919c017591e70782fb0ad92167a160f30:

Added check when fetching and updating translations from Transifex

So as syntax errors in po files don't go unnoticed. Refs #20695.

[Claude Paroz <claude@…>]

In 295a925ceffb0499614bfbe0fb657440b7cf5b9c:

[1.6.x] Added check when fetching and updating translations from Transifex

So as syntax errors in po files don't go unnoticed. Refs #20695.
Backport of 63b215591 from master.

[Claude Paroz <claude@…>]

In 44df41e5fd151378aee2730c497f82e0db68666a:

[1.5.x] Fixed #20695 -- Fixed contrib.humanize translation syntax errors

Affected language: Mexican Spanish, Mongolian, Romanian, Turkish
Translations for 1.6 and master will be refetched from Transifex.
Thanks ruless at gmail.com for the report.

[omat@…]

This issue popped up again in the Django 1.7 beta 3.

[Claude Paroz]

That's right, translation updates and fixes in the 1.6.x stable branch have not been ported to 1.7.x/master.

[Sasha Romijn]

I'm not entirely following this. If the fixed translations for master were refetched from Transifex 11 months ago, how come these fixes are not in 1.7.x/master already, as that was forked from master much more recently?

[Claude Paroz]

Last time translations were refetched from Transifex, it was in the 1.6.x branch.

[Tim Graham]

Do we need to keep this ticket open? It seems like fetching translations is part of the normal release process.

[Aymeric Augustin]

I agree, this problem will disappear by itself by the 1.7 release.

If I missed something, please reopen and explain what's needed.

[omat@…]

This problem still exists in the release candidate 1. Are you sure it will magically go away with the stable version?

[Claude Paroz]

Yes, it will, but not magically, only when I'll push the updated translations.