It would be extrimly useful to have all translations available in one place

[deschler]

Original author: fedor.ty...@gmail.com (November 14, 2010 14:26:39)

Currently it is so, that you have to go through all your models to find untranslated items, and it is counterproductive if you have many different models and all have to be translated.

Even some script gathering data from different models and storing them into .po file would be useful. Another idea is to have a different backend which would allow to store all translations into one table instead of creating addition fields into existing tables.

I like django-modeltranslation because it is probably the fastest one and doesn't produce extra queries to a database, which is important on production server. But it's hard to organize translator's work and also when you are adding new languages you have to edit manually table by table which is awful.

Original issue: http://code.google.com/p/django-modeltranslation/issues/detail?id=53

[deschler]

From eschler on November 14, 2010 21:25:05 I like the idea of having a central place to handle translations. This could be done in an additional custom admin view. I don't think it's necessary to create an extra table as all required information should already be available to modeltranslation. The main challenge is probably to write a view that scales well with many entries.

[tavaresb]

Have you tried django-rosetta? Do you like the interface for translation that rosetta uses? Should we use something similar to that to translate objects in "batch"?

[deschler]

I have never tried django-rosetta, the screenshots on their project page look good though!

[jpic]

Yes, django-rosetta is cool, even though I prefer vim.

[ryselis]

This is a feature I am interested in and willing to contribute. Is this still relevant to you?

[last-partizan]

@ryselis i think it would be nice to have this implemented.

[ryselis]

@last-partizan My current idea is to create 2 views. First view is a list of models. When you click on a model, it redirects to another view, which contains a table with languages in columns, model objects in rows and current editable translations in cells and a save button, something similar to editable admin changelist. On save it saves all entered translations to corresponding database fields. Validation would also be implemented for field length and field in default language would be required if original field was made blank=False. Does this approach look OK?

[last-partizan]

I think so.

Would also be good to have count of untranslated objects or fields in first view (model list). And maybe ability to filter by translated/untranslated in second view (object list).

[ryselis]

I have a working version for Django 2.2. I could not find which other Django versions should be supported, is this information available?

[last-partizan]

https://github.com/deschler/django-modeltranslation/blob/master/tox.ini

we are testing code against django from 1.11 to 3.0