Multi-language support

[Daniel França]

Hi,

I'm beginning to study Mezzanine, and I think it's amazing.

But I got a little disapointed by the lack of multi language support (to publish in different languages).

There's some easy workaround for this? Maybe creating a new Page based type?

I really need this feature and I don't wanna abandon Mezzanine just because that.

Best Regards,

Daniel França

[Stephen McDonald]

Mezzanine has built-in support for Django's sites apps - so you could potentially run a site per language with a shared database.

There are also a variety of Django apps available for handling content translation, but I can't comment on integrating them with Mezzanine.

2011/11/15 Daniel França <daniel...@gmail.com>

--
Stephen McDonald
http://jupo.org

[Zeus Lalkaka]

I am having a tough time wrapping my head around the way the site per language would work and how the urls would end up looking.

By "Run a site per language" do you mean that one would need separate domains for each language? 

Also, how would one even start setting this up? If I go to Sites admin, it lets me add another site, but that doesn't look like it does anything on its own. 

From what I understand by reading the Sites docs from Django is that once you set up multiple site objects you can associate your content models to those objects. But if that is the case then how does Mezzanine decide which content to display and at which url?

Sorry for the over general questions, but it seems like multi-lingual content is something a lot of Mezzanine users are trying to accomplish and this multi-site approach seems to be the one that can be implemented without requiring additional addons and such. 

[Stephen McDonald]

You generally have the right picture - separate domains for sites, each with their own SITE_ID setting (which maps to the site record in the DB)

The initial sites integration is fairly basic, and doesn't expose the site field in the admin. So each site has its own admin and Mezzanine will assign content to the current site you're logged into the admin for.

The benefit you get is shared DB tables for anything that isn't site related, such as users.