Hi guys, I'm running a "hobby" website with translations for roughly 83 languages and I've taken a thorough look at the available options (as in: Django apps):
* django-modeltranslation: probably a bad idea to create 83 columns for each translated string * django-hvad: never got this to work * django-parler: basically dead, the test suite does not pass on 1.10 and 1.11 and the dev mentioned that he has no time to fix it I've settled on django-parler at the time because it worked pretty well. I know you want to outsource as many features as possible (so do I for my personal projects) but the downside of that is that 3rdparty apps that you rely on can die off pretty quickly and then you're stuck. In this specific case I'm kinda wondering why translation is built into Django with the exception of models. Other frameworks ship this stuff out of the box. I know that there are different ways to implement but I can only think of 2: * put everything into one table * put everything into a translations table and join the required language So why is there no (configurable), built in support for this seemingly basic feature? -- 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 [email protected]. To post to this group, send email to [email protected]. 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/da250935-e431-71cb-e3e8-57e0f4f67a3b%40gmail.com. For more options, visit https://groups.google.com/d/optout.
