From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 704713858284; Tue, 2 Jan 2024 16:37:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 704713858284 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704213476; bh=+rV9HklMbSlZXHkwvep+quC0cws0NSJlR6AJ7c6E0kg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=S3u5oD4g0RDZmE7Eiq0ISOzKglTg2zYw23N5LAoqnzAPmQpk1SmZwYeWqHsg7bp21 b1OmsSRCcazFQEuSKvkkvvx5KVR3m6mqRwqoD74d+/jcFSDt7h3d74c/gPRdt9Bvge lVhKsoCG+92THyWzdMHdYLv2yaPdcm6QgX0czadk= From: "oscar.gustafsson at gmail dot com" To: libc-locales@sourceware.org Subject: [Bug localedata/31205] Inconsistent (mon_)grouping formats Date: Tue, 02 Jan 2024 16:37:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: oscar.gustafsson at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31205 --- Comment #5 from Oscar Gustafsson --- Thanks for the reply. Yes, they behave the same, but for consistency reasons I believe that one of them should be selected.=20 Two reasons: * When trying to understand how to specify these strings, the mix of formats (and redundant information) is rather confusing. * There are other tools relying on these files and it would be better if th= ere are fewer corner cases to handle/optimizations to be done. I've later learnt that -1 is translated into "" by localeconv. Hence, one m= ay suspect that 0;0 works because it translates into three(?) string terminati= on characters. While this clearly works, one can hardly argue that it makes se= nse. For the 3;3 case, it may make sense in the user code to check if there is a single digit and in that case have a fast path. Which 3;3 will never detect. Or put another way: what is the benefit of having inconsistent data that may lead to redundant storage and additional computations? --=20 You are receiving this mail because: You are on the CC list for the bug.=