I’m not sure what you’re implying about toggling the translation fields. If it is about shrinking every translation field into a single one with tabs for each language, go ahead. I know that django-modeltranslation is supposed to allow that but I never had it working. If it is about adding translation fields for conf.Setting that need them (instead of the patchy note that I added lately), I plan to do it this weekend.
As regard to the tests, at first I thought that it wasn’t necessary since django-modeltranslation has its own test coverage. But adding a test for each of the 4 items that were corrected plus another one to check if the TRANSLATED flag is correctly set is a good start. Le mardi 20 mai 2014 03:10:07 UTC+2, Eduardo Rivas a écrit : > > Hey Mathias, a couple of points here. First, do you plan on working on the > admin controls for toggling the different translations fields? I'm asking > because I'll have some free time in the coming weeks, but I don't want to > jump into it if you're planning on doing it yourself. > > Secondly, I wanted to share with you that recently an effort has started > to improve Mezzanine's test coverage. It'd be great if you could write some > tests for the features you've contributed; but if you're short on time, > just coming up with a list of pending tests for model translation will be > of great help. You can share it with me or Steve and they'll be added to > the task list. Thanks a lot! > > > 2014-05-19 10:04 GMT-06:00 Mathias Ettinger > <[email protected]<javascript:> > >: > >> I read a bit on ugettext and ugettext_lazy and I agree that we should not >> move everything to plain ugettext. Using ugettext for the default value >> seems perfectly acceptable though. Since pregenerated content into the >> database is populated using the default language translation, it is exactly >> the same behavior. And django-modeltranslation will copy value based on >> that translation anyway. (./manage.py update_translation_fields) >> >> I found the time to make a last change to the settings admin page. It’s >> far from perfect, I have an idea on how to make it more like pages with >> every fields exposed but not much time for that. And at least it’s better >> than nothing. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Mezzanine Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/mezzanine-users/VXVfCU8OFGk/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
