Re: Translations update for Plone 4.0.1

TsungWei Hu <[email protected]>
Newsgroups gmane.comp.web.zope.plone.internationalization
Message-ID <[email protected]>
Though I do not check out latest plone.app.contentrules to verify, the
following line in plone.po
#. Default: "&e = the triggering event, &c = the context, &c = the user"
should be
#. Default: "&e = the triggering event, &c = the context, &u = the user"

Hope this helpful.

/marr/

On Wed, Sep 29, 2010 at 5:01 AM, Vincent Fretin <[email protected]>wrote:

> Hi,
>
> Plone 4.0.1 is soft released.
> I resynced the translations, you have about 10 messages to translate
> from plone.app.contentrules thanks to several i18n fixes made by
> Thomas Desvenain on this package.
> Eric, please wait a new release of plone.app.locales before doing the
> Plone 4.0.1 release. When is the deadline?
>
> You have now up to date statistics at
> http://www.transifex.net/projects/p/Plone/
> With Jean-Michel (toutpt), we managed to fix the configuration to show
> you correct statistics.
>
> Cheers
> Vincent
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Plone-i18n mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-i18n
>

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

_______________________________________________
Plone-i18n mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-i18n
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.