mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Olivier Goudron <olivier.goudron@gmail.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: Call for locales maintainer & contributors
Date: Sat, 26 Jul 2014 15:27:25 +0200	[thread overview]
Message-ID: <CABv4eg1C_5SOuGR4GsZVHW6uQ7J4jx3jpUqcCwEmCwKWCFaUUg@mail.gmail.com> (raw)
In-Reply-To: <20140724193205.GA5498@brightrain.aerifal.cx>

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

Hello,
I don't know how locale files work but i can help for the french
translation if needed.

Olivier.



2014-07-24 21:32 GMT+02:00 Rich Felker <dalias@libc.org>:

> 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
>

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

  reply	other threads:[~2014-07-26 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 19:32 Rich Felker
2014-07-26 13:27 ` Olivier Goudron [this message]
2014-07-26 21:27   ` Wermut
2014-07-27  3:27     ` Rich Felker
2014-07-27 19:43       ` Wermut
2014-07-27 20:41         ` Rich Felker
2014-07-28  3:12         ` Isaac Dunham
2014-07-28  3:28           ` Rich Felker

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=CABv4eg1C_5SOuGR4GsZVHW6uQ7J4jx3jpUqcCwEmCwKWCFaUUg@mail.gmail.com \
    --to=olivier.goudron@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).