I18NFolder migration

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?

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?

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?

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?


Thanks for reading this far, and for any help!

-- 
Fulvio Casali

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

_______________________________________________
Plone-i18n mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-i18n