Hi, We are using modeltranslation in Speedy Net. We currently use it in 2 models - User and SiteProfile of Speedy Match. We currently support 2 languages - en (English) and he (Hebrew). I checked the (local) tables and I found out that every field that we use modeltranslation for, such as first_name in the model User - has 3 columns in the table - first_name, first_name_en and first_name_he. It seems to me that the first one (first_name) is not necessary and I don't understand why we need this field in the table. If I enter the admin interface for the same user - in English and Hebrew I see different values in this field. Is it a bug in modeltranslation or didn't we use it correctly? I don't want each field to be saved in 3 different columns, only 2 as the number of languages we have. The first field is not necessary and I'm not sure it is read from the table at all. Anyway the field (such as first_name) should be equal to the field in the language we are using now (according to the URL of the website). Is this the way it's supposed to be?
I checked and found out there is already an issue on the modeltranslation GitHub website: https://github.com/deschler/django-modeltranslation/issues/488 I didn't check all the 124 open issues there if other issues are also related. Thanks, אורי (Uri) u...@speedy.net -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABD5YeHPuLEy3k%2BAzahidzGioZ7YxCRODVV9bK%2BUnowD8xh%2BSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
