#803361 podebconf-report-po should handle non-ascii chars properly instead of replacing them with ?

#803361#5
Date:
2015-10-29 09:05:14 UTC
From:
To:
I just sent out a request for translations, but a lot of the translator names
have question marks in them while the template has the proper spelling.

I would appreciate it when the names for the translators were used correctly
instead of replacing all non-ascii characters by a question mark.

Paul

- -- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (60, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages po-debconf depends on:
ii  gettext          0.19.3-2
ii  intltool-debian  0.35.0+20060710.1
ii  perl             5.20.2-3+deb8u1

Versions of packages po-debconf recommends:
ii  libmail-sendmail-perl         0.79.16-1
ii  perl [libcompress-zlib-perl]  5.20.2-3+deb8u1

Versions of packages po-debconf suggests:
pn  libmail-box-perl  <none>

- -- no debconf information
iQEcBAEBCAAGBQJWMeE+AAoJEJxcmesFvXUKokQH/2c+YKiai7b/Ug6MQoMO4Bto
9mRMqcxV+qmzZRezNEuLw5o6WTCszhnR+u7oBSLTDb4/ck1BVvrcUVjaawZA2BIk
it8I7vVRn+0D2e18sxDYUC4MwflwGYTz/i93KS3F9igTEG/0XF7K8RwFmoeC2dLI
rbfWI9So+sFrjeTCGrRKLe+ivocO7tu7nD+tx+m0IrxftGBMub1+HD35t3ApTnuB
Loh0f+i918nUT9OSghEnt8atWjz2XIIVXCyWl6NTGOPTOzn//QxoTkZBOrH4eom4
bjHvoHfqK8cSgoi7enqiXJdBhAcczogNPNNuG4M/ZamgfrJWfCast4v4iY5TM4o=
=mAxJ
-----END PGP SIGNATURE-----

#803361#10
Date:
2015-10-29 10:51:45 UTC
From:
To:
Hi Paul,

Le 29/10/2015 05:05, Paul Gevers a écrit :

It’s been a while since I used it, but can’t remember such a problem.
Did you actually use the --utf8 switch?

Regards

David

#803361#15
Date:
2015-10-29 10:57:00 UTC
From:
To:
Hi David,

Nope. I looked in the man page, but fully missed that option. Shouldn't
this be the default behavior nowadays (yes I can set that locally I see
now)?

(Maybe a stupid side remark, but I expect this option plays nice with
translations in non-utf8 codepages as well, right?)

Paul