On Mon, Nov 09, 2009 at 12:48:03PM +0100, Raphael Hertzog wrote: > I don't know if it's col's fault or if it's man-db that does not use col > properly but since col changed recently (and not man-db), I filed the bug > against col. Note that dropping LANG=C makes the warning go away so it's > most certainly locale related. Using any other locale seems to work, even > one that is not UTF-8.
Please see #555330 for some details as I already saw the same thing. What happens is that col sets the locale accordingly (to C) and then reads the document using getwchar(). This operation returns the error you mentioned upon reading the UTF-8 hyphen (e2 80 90). To me this doesn't look like a bug in col, but an incorrect call from lintian as man is asked to produce UTF-8 encoding while col isn't switched to it. Apparently the C locale does not define the encoding. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
