| 1 | | The admin javascript is using django.views.i18n for translation. I have added some cutom javascript to the admin, which needs i18n, too. It turned out that it is not that easy to add own translated texts to the admin, without adding another view function to each ModelAdmin that generates i18n javascript. You can subclass the AdminSite and override the i18n_javascript method, but that is not much convinient and you can not have translations per app or model. I have written a patch that moves the i18n_javascript method from the ModelSite to the ModelAdmin. In addition it adds the app of the ModelAdmin to the list of translation packages. So you can add own javascript translations, by just adding them to the app directory. |
| | 1 | The admin javascript is using django.views.i18n for translation. I have added some custom javascript to the admin, which needs i18n, too. It turned out that it is not that easy to add your own translated texts to the admin, without adding another view function to each ModelAdmin that generates i18n javascript. You can subclass the AdminSite and override the `i18n_javascript` method, but that is not much convenient and you can not have translations per app or per model. I have written a patch that moves the i18n_javascript method from AdminSite to ModelAdmin. In addition it adds the app of the ModelAdmin to the list of translation packages. So you can add your own javascript translations, by just adding them to the app directory. |