It's better if TranslatableAdmin changes the admin form in place, so that there is no need for TranslationInlines.

[bbmokhtari]

Is your feature request related to a problem? Please describe.
Currently the way to manage the translations in the admin is to inherit the admin from TranslatableAdmin and add TranslationInline as its inline.
It's better if TranslatableAdmin changes the admin form in place, so that there is no need for TranslationInlines.

Describe the solution you'd like
Each translatable field should be duplicated in the admin form for each supported language. so if name is a translatable field, there should be name (en - default), name (de), etc. for all the languages. If the field is required (blank=False) the default language field should be required as well, but not other language fields.
This way the admin inlines can manage translations as well and they are not restricted because of the inline limit issues in Django.

[fabiocaccamo]

Frankly I love how django-modeltranslation customizes the admin using jquery tabs, I think that it's the best solution. Is it planned to do something similar?

[bbmokhtari]

Hey there. First of all thanks for being honest. Second, no, it just means adding new fields next to the translatable fields for other languages than the default one. Although I like your proposition and I'll consider it.
Also let me be honest with you too. This update will be a major update in semantic versioning (2.0.0). It will need a lot of change and may not be released until a couple of months. So if you're looking to use a library right now I'd recommend you using whatever you think is best (django-modeltranslation is very mature.)
Any way I wish you good luck mate!