[Hugin-devs] [Bug 1558251] Re: Freench translation update

2016-06-01 Thread tmodes
** Changed in: hugin Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1558251 Title: Freench translation update Status in Hugin: Fix Released Bug

[Hugin-devs] [Bug 1558251] Re: Freench translation update

2016-05-29 Thread tmodes
** Changed in: hugin Milestone: None => 2016.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1558251 Title: Freench translation update Status in Hugin: Fix Committed Bug

Re: [Hugin-devs] [Bug 1558251] Re: Freench translation update

2016-03-20 Thread JeanLucCoulon
Ok, I will avoid to remove obsolete templates.. With tools like lokalize it can be automatically deleted but if the project is correctly configured, the memory translation keep trace of old ones. Anyway, msgmerge -o has a strange behaviour which is not consistent with msgmerge -U Thanks and

[Hugin-devs] [Bug 1558251] Re: Freench translation update

2016-03-20 Thread tmodes
Okay, managed to merge the translations. The main problem was that *you* removed all unused translations from your file. This confused msgmerge when merging with the old version which still have these unused entries. Please leave the unused entries in the po file. As further cause - as already

[Hugin-devs] [Bug 1558251] Re: Freench translation update

2016-03-19 Thread tmodes
Sorry, I can't apply the file in current state. When merging your file with the existing fr.po file I get a new fr.merged.po (msgmerge -o fr.merged.po fr.new.po fr.po) which includes too much translations: msgfmt -c --statistics fr.merged.po 1642 translated messages, 7 fuzzy translations. But it