Your message dated Fri, 18 Mar 2005 03:32:54 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300152: fixed in txt2man 1.4.8-2
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Mar 2005 00:02:14 +0000
>From [EMAIL PROTECTED] Thu Mar 17 16:02:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pcp05454496pcs.sandia01.nm.comcast.net (balefire.icecavern.net) 
[68.35.95.14] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DC4wP-00016y-00; Thu, 17 Mar 2005 16:02:13 -0800
Received: from tonberry.icecavern.net (tonberry.icecavern.net [10.0.0.9])
        by balefire.icecavern.net (Postfix) with ESMTP id 587042ECED
        for <[EMAIL PROTECTED]>; Thu, 17 Mar 2005 17:04:39 -0700 (MST)
Received: by tonberry.icecavern.net (Postfix, from userid 1000)
        id A6887239A7; Thu, 17 Mar 2005 17:02:47 -0700 (MST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Wesley J. Landaker" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: txt2man: generated man pages do not escape hyphens correctly
X-Mailer: reportbug 3.8
Date: Thu, 17 Mar 2005 17:02:47 -0700
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: txt2man
Version: 1.4.8-1
Severity: important

Manpages generated by txt2man do not correctly escape hyphens. While
this doesn't seem to cause any problems with some locales, this ends up
making hyphens disappear when man pages are viewed with many locales.
(Including en_US.UTF-8, which is one reason I noticed this in the first
place!)

This bug is actually pretty important, because I use txt2man to generate
man pages for most of my packages! =)

The fix is to make all hyphens in the output file be backslash escaped,
i.e. '\-' instead of plain '-'. I haven't looked at the code yet, but I
may be able to submit a patch for this.

-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.9-10-amd64-k8
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages txt2man depends on:
ii  gawk                          1:3.1.4-2  GNU awk, a pattern scanning and pr

-- no debconf information

---------------------------------------
Received: (at 300152-close) by bugs.debian.org; 18 Mar 2005 08:53:09 +0000
>From [EMAIL PROTECTED] Fri Mar 18 00:53:09 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DCDEC-00024r-00; Fri, 18 Mar 2005 00:53:08 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DCCuc-00036Z-00; Fri, 18 Mar 2005 03:32:54 -0500
From: Fredrik Steen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#300152: fixed in txt2man 1.4.8-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 18 Mar 2005 03:32:54 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Source: txt2man
Source-Version: 1.4.8-2

We believe that the bug you reported is fixed in the latest version of
txt2man, which is due to be installed in the Debian FTP archive:

txt2man_1.4.8-2.diff.gz
  to pool/main/t/txt2man/txt2man_1.4.8-2.diff.gz
txt2man_1.4.8-2.dsc
  to pool/main/t/txt2man/txt2man_1.4.8-2.dsc
txt2man_1.4.8-2_all.deb
  to pool/main/t/txt2man/txt2man_1.4.8-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fredrik Steen <[EMAIL PROTECTED]> (supplier of updated txt2man package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 18 Mar 2005 08:50:28 +0100
Source: txt2man
Binary: txt2man
Architecture: source all
Version: 1.4.8-2
Distribution: unstable
Urgency: low
Maintainer: Fredrik Steen <[EMAIL PROTECTED]>
Changed-By: Fredrik Steen <[EMAIL PROTECTED]>
Description: 
 txt2man    - Converts flat ASCII text to man page format
Closes: 300152 300154
Changes: 
 txt2man (1.4.8-2) unstable; urgency=low
 .
   * Fixed watch file. (Closes:#300154)
   * Fixed escaping of hyphens (Closes:#300152) - patch from
     Wesley J. Landaker. Thank you.
Files: 
 c7cd570b76ca28af2a9c9a2f01628342 565 text optional txt2man_1.4.8-2.dsc
 2c7f5b529553810ae8869d40c2f5bdb9 2252 text optional txt2man_1.4.8-2.diff.gz
 0111eb4c48f6d5d51414e0138f7f1615 9332 text optional txt2man_1.4.8-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCOoyl2pHue6WOFk8RAo7DAJ4pk/9XQnpHzDdjNNYx+fVguQFK8wCePidl
lVdRMoA0zO0YsxtuS3L5YNg=
=4xR4
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to