I've been investigating some of the options to get multi-lingual content support into Arkestra.

Here's a brief summary at <https://github.com/evildmp/Arkestra/wiki/Multi-lingual-content>.

Comments on any of these approaches?

The two most suitable - though each presents serious difficulties all the same:

* django-modeltranslation, for the way that it registers the models for translation, whereas most others seem to require rebuilding the models one way or another

* simple-translation, for supporting PlaceholderFields out of the box

Daniele

Hi,

I'm new on Arkestra and I my feeling is that it's exactly what I was
missing from django-cms.

I don't know all technical details in deepth, so maybe this makes no sense
at all but, Why couldn't you use the same solution used by django-cms? you
are already using its plugin system and it handles translations with a
'language' field...

Cheers.

El domingo, 10 de junio de 2012 21:53:00 UTC+2, Daniele Procida escribió:

On Fri, Jun 15, 2012, Carlos Perelló Marín <car...@pemas.net> wrote:

Good question Carlos. We (me, and other developers working on django CMS) have been discussing this at length.

The main problem is that the approach taken within django CMS doesn't lend itself to adoption outside the cms (i.e. the cms module of django CMS) application.

The multilingual solution there is pretty much baked in to the specific way that it uses placeholders, which is different from the way other applications use placeholders.

In cms, Placeholders belong to templates. Outside the cms, placeholders are in PlaceholderFields.

To me the best solution looks like django-hvad - best not because it's ready to use, but because it looks like the most promising one to work with.

Stick around, we will crack it (because we absolutely have to). I just hope it's not going to be too painful.

Daniele