Well, convention or not, can you see why that is a ridiculously fragile convention? From what you're saying, this is how things are done in Django-land though, so it would be awkward for DRF to do something different. Poop. :(
On Wednesday, November 1, 2017 at 11:16:26 PM UTC-7, Jani Tiainen wrote: > > Hi, > > Django and DRF both uses GNU gettext to handle translations. With gettext > it's convention is to use plain English "message id" instead of what Ruby > does. > > Ruby seems to have it's own translation mechanisms which is tailored to be > used with abstract message id's. > > 2.11.2017 2.23 "Steve Jorgensen" <[email protected] <javascript:>> > kirjoitti: > >> Looking at >> http://www.django-rest-framework.org/topics/internationalization/ and >> https://raw.githubusercontent.com/encode/django-rest-framework/master/rest_framework/locale/en_US/LC_MESSAGES/django.po >> >> I see that each msgid value is a full English language message. That >> means that if an application has its own translation(s) for DRF's intrinsic >> messages, they can break if the wording of the messages changes from one >> DRF to the next. >> >> I come from the Rails world where the IDs are symbols that do not change, >> and the actual text for the message in any language is determined through >> I18n. >> >> Is there some way this could be improved in future versions of DRF? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django REST framework" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
