Bug#322933: po-debconf: Creates invalid po files for some reason

2005-09-01 Thread Frans Pop
On Sunday 28 August 2005 00:42, Denis Barbier wrote: Unfortunately I am unable to reproduce this bug. Is it reproducible on one of your machines? Yes, I can reproduce it reliably with: $ dpkg -l gettext po-debconf Desired=Unknown/Install/Remove/Purge/Hold |

Bug#322933: po-debconf: Creates invalid po files for some reason

2005-09-01 Thread Frans Pop
The problem is indeed in msgmerge as I can also reproduce if I run that manually. This may shed some light on it. The problem seems to be in added line breaks. I made a diff between the original and created po files, and when I open that in KDE's kate and switch to UTF-8, I see a box

Bug#322933: po-debconf: Creates invalid po files for some reason

2005-08-27 Thread Denis Barbier
On Sat, Aug 13, 2005 at 07:41:39PM +0200, Frans Pop wrote: On Saturday 13 August 2005 19:19, Denis Barbier wrote: This is intentional, I believe that errors in PO files should never trigger aborts of package building. This way, it is much easier to push for translation updates when freeze

Bug#322933: po-debconf: Creates invalid po files for some reason

2005-08-13 Thread Frans Pop
Package: po-debconf Version: 0.8.23 Severity: important Tags: l10n Hi Denis, This is a bit of a weird bug as I only see it on one of my machines and have never seen it before. I have no idea what the conditions are that cause it. The problem is that when I run debconf-updatepo for, for example,

Bug#322933: po-debconf: Creates invalid po files for some reason

2005-08-13 Thread Denis Barbier
On Sat, Aug 13, 2005 at 06:23:11PM +0200, Frans Pop wrote: Package: po-debconf Version: 0.8.23 Severity: important Tags: l10n Hi Denis, This is a bit of a weird bug as I only see it on one of my machines and have never seen it before. I have no idea what the conditions are that cause

Bug#322933: po-debconf: Creates invalid po files for some reason

2005-08-13 Thread Frans Pop
On Saturday 13 August 2005 19:19, Denis Barbier wrote: This is intentional, I believe that errors in PO files should never trigger aborts of package building. This way, it is much easier to push for translation updates when freeze approaches. Note that this is similar with common PO files,