public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/29511] default/C/POSIX locale is 7-bit (127 characters), must be 8-bit (256 characters) since POSIX Issue 7 TC2/Issue 8
Date: Tue, 30 Aug 2022 12:30:07 +0000	[thread overview]
Message-ID: <bug-29511-131-dismuF6FtD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29511-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29511

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |---

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
Sorry, I had assumed that C was specifically worded in such a way that
implementations could default to UTF-8 if they wanted, and POSIX kept this
possibility.

Not sure what to do about this issue. We had this idea to switch to the UTF-8
character set by default for a long time. It's strange that POSIX no longer
allows that.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-30 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29511-131@http.sourceware.org/bugzilla/>
2022-08-30  7:23 ` fweimer at redhat dot com
2022-08-30 11:33 ` nabijaczleweli at nabijaczleweli dot xyz
2022-08-30 12:30 ` fweimer at redhat dot com [this message]
2022-08-30 16:06 ` nabijaczleweli at nabijaczleweli dot xyz
2022-08-30 16:07 ` nabijaczleweli at nabijaczleweli dot xyz
2023-06-28 19:18 ` bruno at clisp dot org
2023-06-28 20:12 ` sam at gentoo 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-29511-131-dismuF6FtD@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: link
Be 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).