From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23720 invoked by alias); 12 Nov 2013 14:39:36 -0000 Mailing-List: contact libc-locales-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-locales-owner@sourceware.org Received: (qmail 23626 invoked by uid 89); 12 Nov 2013 14:39:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_BLOCKED,RDNS_NONE,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Message-ID: <52823D8C.5060309@redhat.com> Date: Tue, 12 Nov 2013 14:39:00 -0000 From: "Carlos O'Donell" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Keld Simonsen CC: Troy Korjuslommi , Steven Abner , libc-locales@sourceware.org Subject: Re: locale encodings References: <31AACAB8-A716-47CC-B755-F33DD77BA51E@zoomtown.com> <1384174607.4028.8.camel@uno11.loco> <20131112012257.GA31828@rap.rap.dk> <5281BEB1.2010909@redhat.com> <20131112133642.GA22738@rap.rap.dk> In-Reply-To: <20131112133642.GA22738@rap.rap.dk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-q4/txt/msg00080.txt.bz2 On 11/12/2013 08:36 AM, Keld Simonsen wrote: > On Tue, Nov 12, 2013 at 12:37:53AM -0500, Carlos O'Donell wrote: >> On 11/11/2013 08:22 PM, Keld Simonsen wrote: >>> Well, the encoding of the source coode of all locales should be 7-bit ascii, for >>> maximum portability. Then the target encoding should be recorded via the >>> % charset specification, which gives a list of possible charsets, comma separated. >>> UTF-8 should always be included there, but other encodings should also be available. >> >> So one of the points that we've been trying to gather consensus on is: >> Is it really important to have 7-bit ASCII? Why not use UTF-8 for the >> the locale source? It's readily readable by all editors and allows >> language specific comments in teh source files for maximum maintenance. > > I think to have UTF-8 is a bad idea, eg for embedded systems, and for systems that is > not maintained in UTF-8. It also can give trouble when communicating the source. Sorry, could you please expand on that? Do you have examples of embedded systems that use glibc locale source and don't support UTF-8? All such embedded systems that I know of run Linux and do support UTF-8. What do you mean by "systems that is [sic] not maintained in UTF-8?" What kind of problems do you forsee when communicating the source? Cheers, Carlos.