Your message dated Thu, 12 Jul 2007 21:48:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#298498: libglib2.0-0: libiconv instead of libc6's iconv()
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 ---
Subject: libglib2.0-0: libiconv instead of libc6's iconv()
Package: libglib2.0-0
Version: 2.6.3-1
Severity: wishlist
Tags: l10n
*** Please type your report below this line ***
I found that at least one usefull codepage isn't
known by glibc. It is KOI8-RU.
So, what about using libiconv ?
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages libglib2.0-0 depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
This is a followup for Debian bug <http://bugs.debian.org/298498>.
On Mon, Mar 07, 2005, Oleg Verych wrote:
> I found that at least one usefull codepage isn't
> known by glibc. It is KOI8-RU.
>
> So, what about using libiconv ?
It seems libiconv is still not packaged; if you don't mind, I'm closing
this bug, as I think it's unlikely that libiconv will ever be packaged.
Please reopen it if necessary.
Bye,
--
Loïc Minier
--- End Message ---
