public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "akihana at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/10392] New: iconv's CP932 doesn't recognize apparently valid input Date: Wed, 15 Jul 2009 08:03:00 -0000 [thread overview] Message-ID: <20090715080338.10392.akihana@gmail.com> (raw) I'm running sys-libs/glibc-2.9_p20081201-r2 on Gento Linux. I'm attempting to use iconv to convert sjis/cp932 input into utf8 output. However, some apparently valid input is causing iconv to return EILSEQ. It is worthwhile to note that this content can be displayed by Firefox both on Linux and a Windows Vista test box as well as in IE8. It appears that there is some problem within iconv, but there is no other charset that matches the input (as seen here): http://www.gnu.org/software/libiconv/documentation/libiconv/iconv_open.3.html -- Summary: iconv's CP932 doesn't recognize apparently valid input Product: glibc Version: 2.9 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: akihana at gmail dot com CC: glibc-bugs at sources dot redhat dot com GCC build triplet: x86_64-pc-linux-gnu GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: x86_64-pc-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=10392 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-07-15 8:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-15 8:03 akihana at gmail dot com [this message] 2009-07-15 8:08 ` [Bug libc/10392] " akihana at gmail dot com 2009-07-16 7:34 ` akihana at gmail dot com 2009-07-17 5:55 ` drepper at redhat dot com 2009-10-30 5:53 ` drepper at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20090715080338.10392.akihana@gmail.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).