Thanks, Karen. I was using gettext, and replacing it to ugettext
indeed fixed the problem.
On Sep 7, 7:06 pm, Karen Tracey <kmtra...@gmail.com> wrote:
> On Mon, Sep 7, 2009 at 12:53 PM, Miklos <miklos.ko...@gmail.com> wrote:
>
> > Hi,
>
> > I have models with verbose names translated into Hungarian. The
> > verbose names contain non-ascii characters. I have trouble adding,
> > editing, or deleting related objects through an admin inline. The
> > error I get is below. I can add, edit, delete them perfectly fine
> > directly through their own admin.
>
> > Has anyone seen this before? Is this a bug of admininline or am I
> > doing the something wrong?
>
> > Thanks,
>
> > Miklos
>
> > models.py
> > ---------------
> > class Topic(models.Model):
>
> > class Meta:
> > verbose_name = _('topic')
>
> What is _ here? If it's ugettext I don't think you will have a problem. If
> it's gettext (but why?), there is a bug in admin in this area, see:
>
> http://code.djangoproject.com/ticket/11710
>
> A simple workaround until it is fixed in Django is to always use unicode
> strings, not byte strings, for your verbose_name values.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
