Your message dated Tue, 30 Jun 2009 13:25:18 +0100
with message-id <1246364718.19026.15.ca...@durandal>
and subject line Re: Bug#528670: /usr/share/info/ledger.info.gz: GBP symbol
displayed incorrectly in documentation
has caused the Debian Bug report #528670,
regarding /usr/share/info/ledger.info.gz: GBP symbol displayed incorrectly in
documentation
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
528670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528670
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ledger
Version: 2.6.1-3
Severity: minor
File: /usr/share/info/ledger.info.gz
In section 3.3 of the documentation, the British Pound symbol is displayed
with the U+FFFD REPLACEMENT CHARACTER rather than U+00A3 POUND SIGN.
I think this is because the info file is encoded with latin1 rather than UTF-8.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (530, 'testing'), (520, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-rc4 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ledger depends on:
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libexpat1 2.0.1-4 XML parsing C library - runtime li
ii libgcc1 1:4.4.0-4 GCC support library
ii libgmp3c2 2:4.2.4+dfsg-2 Multiprecision arithmetic library
ii libpcre3 7.8-2 Perl 5 Compatible Regular Expressi
ii libstdc++6 4.4.0-4 The GNU Standard C++ Library v3
ledger recommends no packages.
ledger suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> Seems like someone's already found and reported this some time ago, in
> #212549. Am I OK to close off this bug?
Fair enough--closing now. :)
--
Sam Morris <[email protected]>
--- End Message ---
