[kupu-dev] kupu-fr.po file still causing problems after upgrade to 1.4.11?

[Duncan Booth]

sisi <sisi at foei.org> wrote:

> This also does not help. Is there anything else I should be doing to get 
> this fixed? I can't tell if my plone site is picking up the new version 
> of kupu, it used to be simple to see this prior to plone 3 with the 
> portal quickinstaller, but I don't know how to check that anymore. I am 
> reluctant to use portal_setup to reload my site because I get an error 
> making a snapshot (which is a whole other story) and generic setup 
> scares the pants off of me :-P
> 
> If anyone has any tips I'd appreciate them!

I think the problem is that when Zope picks up a new translation file (.po)
it compiles it to a .mo file. It detects the presence of a new translation 
when the .po is newer than the .mo, but that means that if the translations 
are created on another system you can get a new .po which is older than 
your .mo and Zope just ignores it. (I could be wrong in this assessment, I 
haven't checked it in that much detail).

Usually deleting the translations from the TranslationService will cure 
this. Next step since that hasn't worked I would guess would be to delete 
the .mo files (in Plone 3.x they should be in parts/<instance>/var/pts

Failing that, find all kupu-fr.po files on your system and delete all but 
the correct one. If you are still picking up an older kupu for some reason 
just copy the newer kupu-fr.po on top of the old one.