mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alastair Houghton <>
To: Rich Felker <>
Subject: Re: [musl] setlocale() again
Date: Tue, 05 Sep 2023 13:57:57 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

On 10 Aug 2023, at 16:51, Rich Felker <> wrote:
> On Thu, Aug 10, 2023 at 04:41:38PM +0100, Alastair Houghton wrote:
>> I spent some time today looking at the setlocale() problem and
>> thought I’d put some notes down in an email.


> At this point, it's been quite a while since I looked at the
> mechanisms. If you'd like to help move this forward, rather than
> starting with a patch, writing a high-level natural language
> description of how you'd make the changes (in terms of musl's current
> internal representation for locale state) would be the most helpful.
> If I'm forgetting and there's already such a good description, just
> digging it up and citing it might be fine.

I wrote something up here:

Let me know what you think; I can update the document there until we’re happy that we’ve got the right solution, then I should be able to create a patch and get the relevant permission from my employer to submit it.

Kind regards,


[-- Attachment #2: Type: text/html, Size: 7636 bytes --]

  reply	other threads:[~2023-09-05 12:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 15:41 Alastair Houghton
2023-08-10 15:51 ` Rich Felker
2023-09-05 12:57   ` Alastair Houghton [this message]
2023-09-18 14:18     ` Alastair Houghton
2023-10-27 20:15       ` Pablo Correa Gomez
2023-11-28 16:27         ` Alastair Houghton
2023-11-28 23:15           ` Pablo Correa Gomez
2023-11-28 17:32       ` Alastair Houghton
2023-11-28 23:21         ` Pablo Correa Gomez

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 NNTP newsgroup(s).