Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 6 Jun 2015 20:24:59 -0400
From: Rich Felker <>
Subject: Re: [PATCH] Byte-based C locale, draft 1

On Sun, Jun 07, 2015 at 01:59:53AM +0200, Harald Becker wrote:
> On 07.06.2015 01:10, Rich Felker wrote:
> >I'm not clear whether your comments are about the proposed byte-based
> >C locale (the patch you're replying to) or about existing code in
> >musl. Could you be more specific?
> I used the discussion about the locale stuff to hop in and ask for
> getting the most wanted feature I'm looking for:

OK, so I'll take this as mostly unrelated to the patch.

> A bare bone (shared) library without all this locale, wchar_t and
> multi byte overhead. Just having a library which always assume C
> locale and UTF-8 byte streams, as I ought all this locale stuff is a
> big block of code, which I heavily dislike and never use (got my own
> UTF-8 handling when and where required). This library with disabled
> locale stuff should otherwise still be compatible, just adding the
> bare minimum of overhead on those locale functions (allowing only
> the single C locale).
> Is that specific enough?

It's somewhat more clear what you're talking about, but I'm still not
sure what specific pieces of code you would want to omit from
Which of the following would you want to remove or keep?

- UTF-8 encoding and decoding
- Character properties
- Case mappings
- Internal message translation (nl_langinfo strings, errors, etc.)
- Message translation API (gettext)
- Charset conversion (iconv)
- Non-ASCII characters in regex and fnmatch patterns/brackers


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.