SmileyChris wrote: > I should have clarified that for this model, I have it's __unicode__ > method return a safe string: > > return mark_safe('%s <small>(%s contacts)</small>' % > (escape(self.name), self.contacts_total)
Hm... I give up then :-). From my looking around the code I think it should behave as you expect because capfirst being a stringfilter should call force_unicode on the object and return a SafeUnicode instance. P.S. However I think you try to shoot yourself in the foot by tying general unicode representation of an object to work only for HTML. I'd rather leave it to some special filter. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---