Arguably dpkg could be enforcing the policy requirement that all package fields be UTF8-encoded. However, that doesn't help users who have already installed this package - dpkg isn't going to scrub this data for already-seen packages. The consumers of this data really need to cope with the wrong encodings.
Arguably dpkg could be enforcing the policy requirement that all package fields be UTF8-encoded. However, that doesn't help users who have already installed this package - dpkg isn't going to scrub this data for already-seen packages. The consumers of this data really need to cope with the wrong encodings.