public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "oscar.gustafsson at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/31206] New: Incorrect value for C-locale (mon_)grouping Date: Tue, 02 Jan 2024 13:44:46 +0000 [thread overview] Message-ID: <bug-31206-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31206 Bug ID: 31206 Summary: Incorrect value for C-locale (mon_)grouping Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: manual Assignee: unassigned at sourceware dot org Reporter: oscar.gustafsson at gmail dot com CC: mtk.manpages at gmail dot com Target Milestone: --- The manual states: "In the standard ‘C’ locale, both grouping and mon_grouping have a value of "". This value specifies no grouping at all." However, the value is -1/CHAR_MAX https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/C;h=fc0614e551519c6b162379bf672b428dba21c12a;hb=refs/heads/master#l73 Not a big deal, but when trying to understand how it actually works, I stumbled upon this. Also, it is not mentioned earlier that an empty string should give this behavior, rather it says that when finding a string termination character, it should use the previous char. Location of the incorrect statement: https://sourceware.org/git/?p=glibc.git;a=blob;f=manual/locale.texi;h=f6afa5dc44a2a016df5c529dc8d2491b689f4b37;hb=HEAD#l702 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-02 13:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 13:44 oscar.gustafsson at gmail dot com [this message] 2024-01-02 14:11 ` [Bug manual/31206] " schwab@linux-m68k.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-31206-131@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).