Re: I18NFolder migration

Maurits van Rees <m.van.rees-1kr/[email protected]> Wed, 26 Sep 2012 11:29:11 +0200
Newsgroups gmane.comp.web.zope.plone.internationalization
Organization Zest Software
Message-ID <[email protected]>
Hi Fulvio,

Op 25-09-12 19:52, Fulvio Casali schreef:
> I am going to preface this email by saying that this is the first time
> I'm working on a multi-lingual site, so any comment or suggestion is
> welcome, as it's likely news to me.
>
> I am upgrading a Plone 2.1.4 site to the latest 4.2, and the entire
> content is fully translated from english into spanish, french and
> arabic.  It's not a very large site, but it still has 658 objects in
> portal_catalog.  First off then, are there any common strategies,
> caveats or tricks for migrating a site that are specific to multilingual
> content?

No.  For the sites I have migrated, I do not remember multilingual problems.

> The main issue, however, is that this site has the I18NFolder product
> installed, with 150 objects of the I18NFolder content type in
> portal_catalog..  It seems like this product was never updated since
> Plone 2.1.4, and indeed, on Plone 2.5.5 all these objects are broken.
> What would be the best way to migrate these objects?

I have not used this product.

> Also, it seems like the goal of the I18NFolder was worthwhile, as I
> understand it, i.e. having a single folder to contain all translations,
> instead of multiple language trees.  How is this achieved in more
> "modern" implementations?

Products.LinguaPlone is the standard here.  In the future, 
plone.app.multilingual could become the preferred solution.

Both products now create separate language folders (en, es, etcetera) in 
the Plone Site root when you install them.  I think you can still choose 
to ignore this and simply create your content in the Plone Site root.

I would say, try it out in a fresh Plone 4.2 site with latest 
Products.LinguaPlone and experiment a bit to see if it works for your 
use case.

> Finally, another product that is installed on the old site is
> PloneLanguageTool, which has not seen any upgrades since the Plone 3
> days.  What should I do with this?

This product is in core Plone, so the standard Plone migration should 
handle any needed changes for this tool just fine.

Best,

-- 
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/