Re: state of plone.app.multilingual?

Hi Asko,

thanks for the reply!

I've started a branch with archetypes fixes:
https://github.com/plone/plone.app.multilingual/commits/thet-fixes

mostly it contains a split profile. there is a base profile, which
doesn't try to alter the plone.app.contenttypes based types, which i
include in this archetypes.multilingual branch:

https://github.com/plone/archetypes.multilingual/tree/2.0

but there is still much to do. known issues:

- 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.

- 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...


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?
https://github.com/plone/plone.app.multilingual/blob/thet-fixes/devel/plone/app/multilingual/browser/menu.py#L49
removing the language neutral check let me translate the content to any
untranslated target language.
not sure about the sensefulness of this usecase.

best, johannes




On Tue, 2014-03-04 at 15:16 +0000, [email protected] wrote:
> Hi Johannes,
> 
> fixing archetypes.multilingual to work with p.a.m. 2.x should be the most futureproof way. (But it would still rely dexterity based "language root folders" so Dexterity must be installed.)
> 
> I have only experience of p.a.m with Dexterity, but whenever the master has issues, which break archetypes.multilingual, I can try to help fixing those.
> 
> Best Regards,
> Asko
> 
> Johannes Raggam kirjoitti Tue Mar 04 2014 12:59:27 GMT+0200 (EET):
> >hi all,
> >
> >can someone (Asko, Ramon) give a short statement about the state of
> >plone.app.multilingual? is the current master ready to be used in
> >production or will there be significant changes? which is the most
> >recent branch? what about archetypes.multilingual? why is there still
> >everything under the devel folder, can't we move that to src?
> >
> >i need a solution for a ongoing project (mostly archetypes based) and
> >have the feeling that Products.LinguaPlone will lock me too much to that
> >solution and plone.app.multilingual 1.x is outdated.
> >
> >
> >best,
> >johannes
> >
> >
> >-- 
> >programmatic  web development
> >di(fh) johannes raggam / thet
> >python plone zope development
> >plone framework  team  member
> >mail: office-//[email protected]
> >web:  http://programmatic.pro
> >      http://bluedynamics.com
> >

-- 
programmatic  web development
di(fh) johannes raggam / thet
python plone zope development
plone framework  team  member
mail: office-//[email protected]
web:  http://programmatic.pro
      http://bluedynamics.com

------------------------------------------------------------------------------
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

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlMYSF4ACgkQW4mNMQxDgAeJEACfaEwmMiEXXbh4V4ThvgMyX76M
GaoAn1wbSk+F8lnUDar1yWqu2xJLg66a
=LyGm
-----END PGP SIGNATURE-----