Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140724193205.GA5498@brightrain.aerifal.cx>
Date: Thu, 24 Jul 2014 15:32:05 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Call for locales maintainer & contributors

With the upcoming locale support in musl 1.1.4, there's going to be a
need to create and maintain locale files for use with musl. This is
not a task I want to take on myself; I feel like it will take away too
much time and concentration from actual further development of musl
and future projects. So I'm looking for someone interested in
maintaining this aspect of musl.

I believe it can (and probably should) be an entirely out-of-tree
project. The intent is for locale files not to be version-specific,
although they may need some updates for future versions of musl when
new messages are added or some of the English messages change.
Otherwise the main task involved is working with users who want to add
full translations or just localized time, monetary, collation, etc.
data.

Since I expect locale support to be somewhat "experimental" in 1.1.4
(note: this should not interfere with existing deployments since the
LC_* vars are basically ignored when MUSL_LOCPATH is not set), I don't
think it's urgent that we get locales created and published right
away. It can be more of an ongoing process. Over the next day or two I
should be committing the rest of the source-level support needed for
LC_TIME and LC_MESSAGES to work. LC_COLLATE and LC_MONETARY might or
might not make it into this release; I'd rather omit them for now and
do them right later than have something hackish in a release that we
feel obligated to continute to support. So early efforts should
probably just be focused on translating day/month names and related
formats and the libc messages.

Rich

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.