The current approach has worked "well enough" for 10 years. I think we can wait a little longer for a better solution rather than change the message format twice. Want to give it a try?
On Tuesday, August 25, 2015 at 11:07:45 AM UTC-4, Ramez Ashraf wrote: > > Dear devs > I'm the PR mentioned contributor. > While I understand your concern about translated content in the database > and the other ticket mentioned (having the info stored as Json or yaml) > I see that these are different ways and are not mutually exclusive. > The issue mentioned regards having multiple supported languages, while > what the PR is solving is the simple "not english " site + the idea of > having a customized label or clear verbose name instead of the current > field name. > > IMHO, I think this pull is a step forward. And when the issue mentioned is > solved in an enhancement of the log structure, the old structure will > continue to exist for backword compatibility. > > I call -if I may- a reconsideration. :) > > Last, I'm making extensive use of the admin in my work.. Hopefully I'll be > around contributing in it. > > Kind regards -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b42297c7-c3bc-4834-8323-579115535854%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
