From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 719DC385E001; Sun, 29 Mar 2020 16:59:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 719DC385E001 From: "carlos at redhat dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: locale X-Bugzilla-Version: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed bug_status cc cf_reconfirmed_on Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2020 16:59:57 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25744 Carlos O'Donell 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 --- (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 wi= th the old behaviour and release that. --=20 You are receiving this mail because: You are on the CC list for the bug.=