public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug locale/25744] mbrtowc with Big5-HKSCS returns 2 instead of 1 when consuming the second byte of certain double byte characters Date: Sun, 29 Mar 2020 16:59:57 +0000 [thread overview] Message-ID: <bug-25744-131-TePhp3OjN8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25744-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25744 Carlos O'Donell <carlos at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |carlos at redhat dot com Last reconfirmed| |2020-03-29 --- Comment #1 from Carlos O'Donell <carlos at redhat dot com> --- (In reply to Tom Honermann from comment #0) > 2nd mbrtowc call: > result: 2 (1 expected, glibc returns 2) > wc: 0x00CA (0x00CA expected) > As noted in the code comments and process output, the return value for the > second call to mbrtowc() is unexpected. My opinion is that this is an implementation defect in the converter which has absolute control over how those return values are computed. My worry though is that changing this now might break existing code that is out there that is using BIG5HKSCS. If that's actually the case then we could create a distinct gconv module with the old behaviour and release that. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-29 16:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-29 4:28 [Bug locale/25744] New: " tom at honermann dot net 2020-03-29 16:59 ` carlos at redhat dot com [this message] 2020-03-30 12:44 ` [Bug locale/25744] " schwab@linux-m68k.org 2020-03-30 15:13 ` carlos at redhat dot com 2020-03-30 17:31 ` tom at honermann dot net 2020-03-30 17:36 ` schwab@linux-m68k.org 2020-03-30 17:38 ` tom at honermann dot net 2020-04-01 4:04 ` tom at honermann dot net 2020-04-07 5:43 ` tom at honermann dot net 2022-07-06 14:20 ` cvs-commit at gcc dot gnu.org 2022-07-06 14:25 ` adhemerval.zanella at linaro dot org
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=bug-25744-131-TePhp3OjN8@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).