Bug 5776 - Some conversions to ISO-2022-JP produce invalid text
Summary: Some conversions to ISO-2022-JP produce invalid text
Status: RESOLVED WORKSFORME
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Ulrich Drepper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-19 21:44 UTC by Aurelien Jarno
Modified: 2014-07-02 07:23 UTC (History)
3 users (show)

See Also:
Host: x86_64-unknown-linux-gnu
Target: x86_64-unknown-linux-gnu
Build: x86_64-unknown-linux-gnu
Last reconfirmed:
fweimer: security-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aurelien Jarno 2008-02-19 21:44:43 UTC 
Converting the following UTF8 sequence to ISO-2022-JP//TRANSLIT, then
back to UTF-8 fails:
$ perl -e 'print join("", map { chr hex $_ } qw/e3 83 a2 ef bd 9e 0a/)' | \
  iconv -f utf8  -t iso-2022-jp//TRANSLIT|iconv -f iso-2022-jp -t utf8
モiconv: illegal input sequence at position 5

Either iconv has generated invalid ISO-2022-JP, or it refuses to accept
valid ISO-2022-JP.
Comment 1 Ulrich Drepper 2008-03-09 01:06:16 UTC 
I cannot reproduce this with the current sources.  Older releases had this
problem.  I haven't investigated what changed.