Think of it this way: It's a bug from upstream. The text in question
certainly it is NOT a bug. Anyone with half a brain can see that.
You think it is wrong only because you don't like it, even it is a standard.
doesn't fit the format of the file, it's a lone exception added purely
for selfish political reasons by a bully. Deleting it will make the
file more self-consistent.
If a technical standard has a bug -- describes something hard or
impossible to implement, or extremely inconvenient for users -- there
may be grumbling and flamewars about it, but in many cases I would say
debian would err on the side of `reasonableness' over slavish adherence
to the standard (one possible example would be things affected by the
POSIX_ME_HARDER, er, I mean, POSIXLY_CORRECT environment variable).
Is this particular part of the standard crucial for proper operation?
E.g., will someone lookup stuff in that file using the exact country
description as an index? I don't know, but I'd say it's pretty unlikely
-- much more probable is that they'll look for the country name (the
part preceding the comma), or use other fields as index to find the
country name. Humans of course can cope either way.
Is it true that nothing can be known? If so how do we know this? -Woody Allen