[Plone-i18n] new translation key best practice

[Paul J Stevens]

Hi all,

I've done a fix for a very long-standing bug

https://dev.plone.org/ticket/7556

where for Archetypes fields the allowable_content_types attribute on
fields is ignored.

I've done this along the same lines as for the 'required' attribute:
show the form with a nice error message. This will however raise
exceptions during the tests since the i18n key is missing from plone.pot.

Adding it to plone.app.locales is no problem.

However, is it valid to resync plone.app.locales's master branch using
the plone-4.2 coredev buildout, where the Products.Archetypes is on the
master branch?

Running i18n-update-all creates quite a diff-stat and I don't want to
upset anyone :-)

thanks.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin

* Premium Hosting Services and Web Application Consultancy *

www.nfg.nl/in...@nfg.nl/+31.85.877.99.97
________________________________________________________________

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Plone-i18n mailing list
Plone...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Vincent Fretin]

Hi,

Sorry for the late reply.
I think we need to create a branch for 4.2.x and master should become Plone 4.3 only.
If somebody can do it and resync with i18n-update-all from Plone 4.3 buildout and eventually fix i18n issues (for example two msgid with different default) , please do.
I'm really out of time lately, any help is appreciated.

Vincent