Your message dated Sun, 5 Sep 2021 11:25:30 +0200
with message-id <ytsncixvmehkv...@aurel32.net>
and subject line Bug#161312: recode: GB18030 conversion has off-by-one error
has caused the Debian Bug report #161312,
regarding recode: GB18030 conversion has off-by-one error
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 ow...@bugs.debian.org
immediately.)


-- 
161312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=161312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: recode
Version: 3.6-6
Severity: normal

When converting to GB18030, the four-byte sequences output for BMP are off
by one codepoint. This is most likely due to implementation of the initial
GB18030 documentation which had a missing mapping for U+0080.

For example, converting U+00A0 to GB18030 results in 81308431 instead of
81308432:

  echo -n   | recode iso-8859-15..gb18030 | od -t x1
  0000000 81 30 84 31

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux peter 2.4.17 #2 mån feb 18 09:17:46 CET 2002 i686
Locale: LANG=sv, LC_CTYPE=sv_SE

Versions of packages recode depends on:
ii  libc6                         2.2.5-11.1 GNU C Library: Shared libraries an
ii  librecode0                    3.6-6      Shared library on which recode is 



--- End Message ---
--- Begin Message ---
Version: 2.3.2-1

On 2002-09-18 11:01, Peter Karlsson wrote:
> Package: recode
> Version: 3.6-6
> Severity: normal
> 
> When converting to GB18030, the four-byte sequences output for BMP are off
> by one codepoint. This is most likely due to implementation of the initial
> GB18030 documentation which had a missing mapping for U+0080.
> 
> For example, converting U+00A0 to GB18030 results in 81308431 instead of
> 81308432:
> 
>   echo -n � | recode iso-8859-15..gb18030 | od -t x1
>   0000000 81 30 84 31

This is not reproducible anymore back to glibc 2.3.2. I believe it has
somehow been fixed between glibc 2.2.5 and 2.3.2, there as been many
changes to the gb18030 iconvdata between these releases. I am therefore
closing the bug.

Regards,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

--- End Message ---

Reply via email to