If we were able to switch to declaring sites as settings rather than as models as described in https://groups.google.com/d/topic/django-developers/OGOf1TfSBBs/discussion, I believe it would be more feasible.
On Tuesday, July 19, 2016 at 7:11:03 PM UTC-4, Shai Berger wrote: > > On Wednesday 20 July 2016 01:43:05 James Pic wrote: > > Hi all, > > > > Are there any plans to make Site.name translatable ? > > > > Site.name is a model field. > > Translatable models are a big hairy issue. Several solutions have been > suggested, each with its own pros and cons. Last time I looked (several > years > ago), we were not at the stage where we could bless one of them. > > > Would that be something we want to offer as a feature ? > > > > Site.name as a single, special-cased translatable field? I don't believe > so. > > Shai. > > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b9956d64-c067-46a8-8ed4-8fd510045603%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
