Have you tried looking through history with git blame to find related tickets? Another tip is to search Google with a query like "javascript_catalog site:code.djangoproject.com". This will let you find tickets to see if the issue was raised before. This is how I try to answer questions like this since many of the original authors are no longer active (or at least, you can find the person who authored the code in question and try a more directed query like a ping in IRC).
On Tuesday, March 1, 2016 at 6:23:38 PM UTC-5, Cristiano Coelho wrote: > > Maybe I wasn't clear neither, but the main issue is this: when using a > language equals to the default one, and if that language does not define > any translation text (because ids are the same as values so it is not > necessary), the server side translations will always correctly return the > translated texts, while the javascript won't because it always has an > english fallback. > Also the code I provided should actually load the default language > translations as well (but not the english ones!) to make it behave exactly > as the server side translations. > -- 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/1a47cef8-395b-4bf4-8c0b-41e3e4e885bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
