From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120064 invoked by alias); 3 Jun 2015 15:57:06 -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 120041 invoked by uid 89); 3 Jun 2015 15:57:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Message-ID: <556F23C9.3030500@redhat.com> Date: Wed, 03 Jun 2015 15:57:00 -0000 From: Marko Myllynen Reply-To: myllynen@redhat.com User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: GNU C Library , libc-locales@sourceware.org Subject: Removing locale timezone information Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-q2/txt/msg00068.txt.bz2 Hi, glibc allows defining timezone as part of locale information but very few locales do it, only 6 out of almost 300 locales implement it. The LC_TIME/timezone keyword is not in POSIX standards (but comes from ISO TR 14652) and the comment in programs/ld-time.c seems to suggest it was not such a good idea to begin with: /* XXX We don't perform any tests on the timezone value since this is simply useless, stupid $&$!@... */ I'm sure nobody wants to even think about duplicating tzdata information in glibc locale files so I propose that, in the name of consistency, we remove the existing timezone definitions from the shipped locale files but leave the actual code still available (to allow any possible custom locales defining it to be used). Thoughts? If there are no objections, I can file a BZ and submit a patch. The locales in question are: km_KH, lo_LA, my_MM, nan_TW@latin, th_TH, uk_UA. Thanks, -- Marko Myllynen