From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5635 Path: news.gmane.org!not-for-mail From: Wermut Newsgroups: gmane.linux.lib.musl.general Subject: Re: Call for locales maintainer & contributors Date: Sat, 26 Jul 2014 23:27:38 +0200 Message-ID: References: <20140724193205.GA5498@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1406410079 10182 80.91.229.3 (26 Jul 2014 21:27:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 26 Jul 2014 21:27:59 +0000 (UTC) To: "musl@lists.openwall.com" Original-X-From: musl-return-5640-gllmg-musl=m.gmane.org@lists.openwall.com Sat Jul 26 23:27:55 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XB9VQ-0006BJ-Gb for gllmg-musl@plane.gmane.org; Sat, 26 Jul 2014 23:27:52 +0200 Original-Received: (qmail 16046 invoked by uid 550); 26 Jul 2014 21:27:51 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 16038 invoked from network); 26 Jul 2014 21:27:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bortis.ch; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=JRw6wryf8ZPmzVE4W7v3Dh+1ufiJEjPR3zR44xhsZ4k=; b=AvqVoGiCfLZdvsj/1GKNhzeH1jt67cFqoN3bX7Jp55hTfs7t6l2yLF117rGvUoJD50 6RY2N/BRHpqm1KnYKYYr0kbx9ST+8ZvbWpwY6/HIIONSRR9+GN6IuTecS7Tojps2d2tR COKrE5qFriyO08LbCBgbYH/gqDjZ1vqtbQJY4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=JRw6wryf8ZPmzVE4W7v3Dh+1ufiJEjPR3zR44xhsZ4k=; b=xtft77ViYBH6pgxX/Jtv/FkemiOauX1jmd19ola1VdDlLH7YclXuLBx3/RWbWTX6dh IwJyy3AwERRPOvxvDA8gB/d6Jh9NiSIa09U0ymFlCVvVF9B1iBqPHBuETirhXmsZjACV XqpB500t5HopEWNflhpa1RhF9p9oHO7bcnTcK7Aga892WCb0Uz1Tx5OCO4PcmxSZ9aZu nx8Aiq9zlHiDcD38BxwMr6b5m13LM/iCCRcgf6ounfLNnXEuE5TBdb9RuE1/O5DtVVtW AVC6GwoClvxUZB0yONT0sT3IGG6tFr0PIGihD6Rkc/Sx2/a69HpPAtbHYH5qfeK9IoBV XF+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=JRw6wryf8ZPmzVE4W7v3Dh+1ufiJEjPR3zR44xhsZ4k=; b=DOrVk2iH3TTjCprkR4uT0/B9P77uU3KkZd4rvrvv7+82cF4IsWdrSbYm5V4xI/K7XF iBTF9Sao5nK+04WNDMvt/Hg8Bq/g/RXI8UTKGAe95SgeQ8d9/ifekll1MqNFXKv0pUF/ YK+XoetDu/0dXiLOfurYH8Jx3P1vCxReOXekc922O7qSVN6om+e0ZCIqrLTG7IcxZkPg XQzeC0VfChFWU/gWqqRPGGWShRZp8beyco2mbr4pVloowiZ01hlowTibyFDk30vZ24ST FuV41g1FsgnvrsZNmHjiv/lo0TAWaTu4SXqudE5olAGYK7XjxCztuNa+RHuSOHyYfy/C mvcg== X-Gm-Message-State: ALoCoQnVb5r/D6w8OgUZNu5Ant6o19Fj9i1TA62A/Qh4rqFUedkWmnf6g2umH6iLKY30MrYeUZuP X-Received: by 10.236.19.196 with SMTP id n44mr37029653yhn.83.1406410058621; Sat, 26 Jul 2014 14:27:38 -0700 (PDT) Original-Sender: kevin@bortis.ch In-Reply-To: X-Google-Sender-Auth: FlY8BbKjtnQ3s1Tsi8wc3KPWk0M Xref: news.gmane.org gmane.linux.lib.musl.general:5635 Archived-At: Hi I don't like the idea of an entirely new tree of locale data written from scratch. Glibc has one (with a lot of unmaintained data) and then there is also the CLDR repository which aims to be the central source for such data, maintained by unicode. The CLDR data is also used as a basis for the Microsoft and Apple locale files and is often maintained by national language experts. What I could offer is an effort to write some magic code that imports the actual CLDR data and converts the relevant information to the musl formatted ones. The CLDR data is freely available from: http://cldr.unicode.org/index/downloads Contribution is not completely open, but you normally interested people get access if they want to. I got mine within a week. This is only a suggestion open to discussion. What do you guys think about it? Regards Kevin On Sat, Jul 26, 2014 at 3:27 PM, Olivier Goudron wrote: > 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 : > >> 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 > >