Your message dated Mon, 17 Sep 2007 01:50:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#235133: man-db: Seems to be partly a groff problem
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: man-db
Version: 2.4.2-9
Severity: normal
Tags: l10n

With LANG=zh_TW.Big5 (or even the debian default of zh_TW.BIG5), "man host"
displays gibberish.  Judging from the look of the gibberish, it seems that
the man command is treating each half of the Chinese characters as ISO-8859-1
characters.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.23-ow1
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5

Versions of packages man-db depends on:
ii  bsdmainutils                6.0.11       collection of more utilities from 
ii  debconf                     1.4.11       Debian configuration management sy
ii  dpkg                        1.10.18      Package maintenance system for Deb
ii  groff-base                  1.18.1-15    GNU troff text-formatting system (
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libgdbm3                    1.8.3-2      GNU dbm database routines (runtime

-- debconf information:
  man-db/build-database: false
* man-db/rebuild-database: true
* man-db/install-setuid: false



--- End Message ---
--- Begin Message ---
Source: man-db
Source-Version: 2.4.4-1

On Tue, May 10, 2005 at 11:52:57AM -0400, Ambrose Li wrote:
> I spent half an hour looking at this. Seems that groff is currently unable
> to handle Big5. So this bug seems to be (at least partly) a groff bug.

Indeed. I believe that this is now fixed on both sides, and subject to
my rather dubious ability to recognise correct Chinese the results look
OK to me:

groff (1.18.1.1-9) unstable; urgency=low

  * Move www.tmac to groff-base (closes: #319506).
  * Fix non-XSI code in groff.postinst (part of #256226).
  * Improve CJK support (closes: #324107):
    - Add support for Chinese GB2312/GBK and BIG5 encodings (in the
      increasingly-misnamed nippon driver), with kinsoku tables borrowed
      from Emacs. Simon Law eyeballed the GB2312/GBK table.
    - Expect UTF-8 input when running under a ko_*.UTF-8 locale. Functional
      Korean support still requires a kinsoku table and a groff font
      covering Hangul.
  * Fix use of DoCharacter() in multibyte case; some calls to it were
    missing the fourth argument (closes: #285524).
  * Policy version 3.6.2. No changes required.

 -- Colin Watson <[EMAIL PROTECTED]>  Wed, 31 Aug 2005 12:54:37 +0100

Wed Aug 31 01:23:55 BST 2005  Colin Watson  <[EMAIL PROTECTED]>

        * src/encodings.c (directory_table): Add Simplified Chinese ->
          GB2312 and Traditional Chinese -> BIG5.
          (charset_table): Use the nippon device for BIG5, GB2312, and GBK.
          (device_table): Assume that the nippon device is
          encoding-agnostic, since it handles several encodings now.
          (compatible_encodings, get_roff_encoding): Extend the ja_JP.UTF-8
          hack to cover zh_CN.UTF-8, zh_SG.UTF-8, and zh_TW.UTF-8 too.

Please file a new bug report if you're still seeing problems.

Cheers,

-- 
Colin Watson                                       [EMAIL PROTECTED]


--- End Message ---

Reply via email to