severity 510613 wishlist merge 480996 510613 thanks On Sun, Jan 04, 2009 at 02:28:21AM +0800, jida...@jidanni.org wrote: > Package: man-db > > I (#508743) saw > $ LC_CTYPE=C man metastore #in emacs > Written by David Hrdeman <da...@hardeman.nu> > in the shell > Written by David Heman <da...@hardeman.nu> > > Ah, > $ man -w metastore|xargs zless|tail -2|uni2ascii -wa P > Written by David HU+00E4 rdeman <da...@hardeman.nu> > > Only when I do > $ man metastore|grep hardeman > <standard input>:63: warning: can't find special character `u4CA4' > Written by David Heman <da...@hardeman.nu> > Do I finally see any error message. > > I'm not sure if the man providers have decided to turn back error > messages on or not, but plain man won't show them, and even a > redundant > $ man metastore|less > will output them at the top whereupon they fly off the screen... > > So some way is needed to show errors or else "All these years I though > he was Mr. Heman."
Dan, I do wish that you would remember the bug reports that you yourself have already submitted, and on whose progress I took the time to update you less than a month ago! It is tedious but understandable to have to deal with multiple instances of essentially the same report from different people; when the instances come from the same person, it is most tiresome and suggests laziness. "Oh, I can't be bothered to remember whether I already filed a bug about this; I know, those Debian folks don't have very much to do or have real lives or anything, so I'll just let them sort it out." See bug #480996. > P.S., no matter what environment settings I use, that unicode char is not > getting through. The manual page should use "\(:a" (as documented in groff_char(7)) rather than literal "รค". At that point it'll be flattened to "a", but at least won't be corrupted. The root cause of this is that groff does not have Unicode input support yet, as documented copiously in other bug reports. Until it does, we have to apply a number of rather gross kludges; you're hitting one of the corner cases in these kludges. Specifically, I rather suspect that you're using a Chinese locale (although you didn't mention this; I only know this from background knowledge based on your previous bug reports). At the moment we have to special-case groff's behaviour in Chinese, Japanese, and Korean locales in order to make CJK manual pages render properly. An unfortunate casualty of this is that non-CJK manual pages that use non-ASCII characters will run into problems when viewed in CJK locales. Once we can feed Unicode data to groff, either directly or through a more capable translation layer than the crude ones we're obliged to use at the moment, this problem will go away. In the meantime, I advise workarounds such as the above. Regards, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
