Multilingual content

[Mabroor Ahmed]

Hi,

We are going to deploy a new webshop and have Cartridge and LFS as the
final two choices. Whereas I would really like to go with Cartridge
(ease of install, easy of extension etc.), I am wondering how to go
about with having multilingual content. Shop has to be in 2-3
languages and Mezzanine, Cartdige does not support it.

How complex would it be to have multilingual content functionality
added to Mezzanine? Has anyone else had success with a third party
extension? Any pointers would be greatly appreciated!

Kind Regards,
Mabroor Ahmed

[POKOLI I PUNTO]

Hi,

Here you can found the discussion we have started some time ago:

https://github.com/stephenmcd/mezzanine/issues/106

And more info in the mailing list:

https://groups.google.com/group/mezzanine-users/browse_thread/thread/1ac7874c1da2f33d/d6737e1b0c7feb4b?lnk=gst&q=language#d6737e1b0c7feb4b

https://groups.google.com/group/mezzanine-users/browse_thread/thread/1830b4dd106ee4fd/c3ddee6f655bf6de?lnk=gst&q=language#c3ddee6f655bf6de



Al 08/06/12 09:38, En/na Mabroor Ahmed ha escrit:

[Stephen McDonald]

I'll also add that this is planned for the 1.2 release - can't give a time frame, but it's definitely next on the plate.

--
Stephen McDonald
http://jupo.org

[POKOLI I PUNTO]

Stephen McDonald <st...@jupo.org> escribió:

>I'll also add that this is planned for the 1.2 release - can't give a
>time
>frame, but it's definitely next on the plate.

Greaaaattt!!! I'm waiting to hear more info about it. If i can help let me know!

>
>On Fri, Jun 8, 2012 at 5:57 PM, POKOLI I PUNTO <pok...@gmail.com>
>wrote:
>
>> Hi,
>>
>> Here you can found the discussion we have started some time ago:
>>
>>

>https://github.com/stephenmcd/**mezzanine/issues/106<https://github.com/stephenmcd/mezzanine/issues/106>

>>
>> And more info in the mailing list:
>>
>>

>https://groups.google.com/**group/mezzanine-users/browse_**thread/thread/*
>>
>*1ac7874c1da2f33d/**d6737e1b0c7feb4b?lnk=gst&q=**language#d6737e1b0c7feb4b<https://groups.google.com/group/mezzanine-users/browse_thread/thread/1ac7874c1da2f33d/d6737e1b0c7feb4b?lnk=gst&q=language#d6737e1b0c7feb4b>
>>
>>
>https://groups.google.com/**group/mezzanine-users/browse_**thread/thread/*
>>
>*1830b4dd106ee4fd/**c3ddee6f655bf6de?lnk=gst&q=**language#c3ddee6f655bf6de<https://groups.google.com/group/mezzanine-users/browse_thread/thread/1830b4dd106ee4fd/c3ddee6f655bf6de?lnk=gst&q=language#c3ddee6f655bf6de>

[Stephen McDonald]

Oh I also forgot - if you read the thread Pokoli linked to, you'll see he started out by getting django-modeltranslation (http://code.google.com/p/django-modeltranslation/) to work with Mezzanine, so there is a solution available right now.

[Stephen McDonald]

No new info at this stage. I haven't done any work but I have been thinking about what's involved. My plan is to pick up where we left off, so to re-cap:

- Models will get marked with some meta-data describing which fields should be translatable

- Those fields will get converted at startup time into some kind of accessor, where instance.field_name will retrieve instance.field_name_LANG

- Each language set up (using the usual approach in settings.py) will create an extra database field for each translatable field per language

- All of the field creation will happen in a similar way to the current setup for EXTRA_MODEL_FIELDS

The big question is how the migrations are managed. I've been thinking about possibly providing an empty app in every project, perhaps called "project_migrations", and have some kind of management command that wraps South's schemamigration command, and creates migration files in that project-level app. I think this is a messy idea, but it's the best I have at the moment. 

The big problems are that south migrations are tied to their apps and these are sequential. So I also thought about looking into other migration tools (I hear of one called nashvegas which is popular), and to see if they provide a better approach that would address these issues.