Re: state of plone.app.multilingual?

Hi Johannes,

just great you are working on this! I'll try out your branch myself
tomorrow.


Johannes Raggam wrote:
> but there is still much to do. known- relocating content doesn't work for me. i get a maximum recursion
> RuntimeError at here:
>
> https://github.com/plone/plone.app.multilingual/blob/thet-fixes/devel/plone/app/multilingual/browser/migrator.py#L126
>
> the content here is a Acquisition aquired archetypes folder within a
> lineage subsite, where calling objectIds() causes the maximum recursion
> error. i aq_base'd the content, got different errors, which i didn't
> look at more deeply yet.

Does it work any better without Lineage? (I'd expect that Lineage +
LanguageRootFolders together can have a lot of issues and they can have
incompatible acquisition/proxying magic in them.)

> - the add_at_translation view doesn't exist yet:
> https://github.com/plone/plone.app.multilingual/blob/thet-fixes/devel/plone/app/multilingual/browser/add.py#L55
> i tried to comment the path out, which let me beyond this traversal
> step. can't remember exactly, what happened then...

I think the view should be implemented in archetypes.multilingual (look
for p.a.multilingual 1.x for the last version) and that traverser should
be abstracted in a way that it does not need to know the path of
AT-translation view.

> not an error, but maybe a usecase:
> - wouldn't it make sense to let language neutral content be translated
> too? e.g. if you have a content with mixed languages in it's text. or
> you don't want to move all of the old content into a language root
> folder?

I think this is still under discussion, because it's a tempting
use-case, but I don't remember all the corner cases for this.

If Ramon is reading this, I hope that he could list the issues.

One known major problem with language neutral / shared content is that
it has to be indexed once for each language in use. So, if we would
encourage people to default on language neutral / shared content and
localize random pages only, it would use the catalog more than if we
would have the same content only under the language root folder for the
default language.

-Asko

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk