search

google-code-export / django-grappelli

Automatically exported from code.google.com/p/django-grappelli
0 stars 0 forks source link

Some Revision after 639 broke datetime display #148

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. using german grappelli in django
2. what was displayed before as 19. Dez. 2009, 03:55 in the overview of a 
class (list_display contains a datetimefield 'publish_date')
3. is now displayed as garbage like  
Frvorm.CET1261109449DezthDezember+0100RDezvorm.CET

Actual Revision as of this writing is 703.

Original issue reported on code.google.com by g4b....@gmail.com on 19 Dec 2009 at 3:24

GoogleCodeExporter commented 9 years ago

Original comment by sehmaschine on 21 Dec 2009 at 10:09

GoogleCodeExporter commented 9 years ago 
strange, but this seems to be a django-issue. I just used the original django
admin-interface and I get this error as well ... so I guess it´s not related to
grappelli.

Original comment by sehmaschine on 21 Dec 2009 at 10:21

GoogleCodeExporter commented 9 years ago 
I'm curious, is there a solution for this problem?
I discovered it using Django 1.0.1 and 1.1.1

Original comment by dot...@googlemail.com on 7 Jan 2010 at 1:41

GoogleCodeExporter commented 9 years ago 
Same problem here using Django 1.1.1.
The date
> 2010-03-19 12:20:31
is displayed as
> Frnachm.Europe1269001231MärthMärz+0000RMärnachm.Europe

After deleting the locale folder (grappelli/locale/) the datetime column is 
displayed
correct.

Original comment by grimm.ma...@gmail.com on 19 Mar 2010 at 12:47

GoogleCodeExporter commented 9 years ago 
OMG the problem is that there's an translation for DATETIME_FORMAT in
grappelli/locale/de/LC_MESSAGES/django.po

msgid "DATETIME_FORMAT"
msgstr "DATUMSFORMAT"

And because of django.utils.translation.trans_real.get_date_formats translated
settings variables are used for this -.-

Perhaps this shouldn't be translated by grappelli?

Original comment by grimm.ma...@gmail.com on 19 Mar 2010 at 12:57

GoogleCodeExporter commented 9 years ago 
Hi,

I hadn't much to do with grappellis internals until I found this issue. I hope 
that
anyone will attend to this issue. For now, I deleted the two lines mentioned by 
grimm.markus and re-compiled the german language file. It's just a dirty 
workaround,
but it works. If you strongly need the workaround, you can replace
grappelli/locale/de/LC_MESSAGES/django.mo with the attached patch.

Original comment by Valentin...@googlemail.com on 26 Mar 2010 at 12:10

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by sehmaschine on 21 May 2010 at 1:45

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r1033.

Original comment by klemens.mantzos on 26 May 2010 at 5:44

GoogleCodeExporter commented 9 years ago 
shouldnt be an issue in 2_1 (no locale dir)

Original comment by klemens.mantzos on 26 May 2010 at 5:44