Le mardi 29 avril 2014 18:34:58 UTC+2, Eduardo Rivas a écrit : > > Django gives two possible choices: mark the url patterns for translation, > or use i18n patterns to prefix the whole site's urls with a lang code (what > the Admin currently does). Is Mezzanine going to favor any particular > approach? >
I tend to prefer solutions that avoid marking slugs for translations since it will require extra tweakings to get every slug auto-populated from the title. I personnally use neither of theses approaches and rely on django sessions to change active language (with a setup very similar to https://docs.djangoproject.com/en/dev/topics/i18n/translation/#the-set-language-redirect-view). It is also possible to use both (translated slug with a lang code prefix) and will only require the same amount of work as translated slugs. Btw, I agree that we need to take a decision: with or without i18n_patterns? and with or without translated slugs? All four choices are valid. It is also possible to postpone this question and integrate translated slug (through a boolean setting?) into an other patch. As a side note, the language selector in the admin is gone in lattest version of mezzanine. Did I miss it somewhere or is the template not rendering it? -- 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.
