public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "keld at dkuug dot dk" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/2388] [PATCH] week-ndays;week-1stday;week-1stweek data for some locales Date: Tue, 11 Apr 2006 20:56:00 -0000 [thread overview] Message-ID: <20060411205607.26678.qmail@sourceware.org> (raw) In-Reply-To: <20060223121603.2388.mmarek@suse.cz> ------- Additional Comments From keld at dkuug dot dk 2006-04-11 20:56 ------- Subject: Re: [PATCH] week-ndays;week-1stday;week-1stweek data for some locales On Tue, Apr 11, 2006 at 09:38:49AM -0000, sbrabec at suse dot cz wrote: > > ------- Additional Comments From sbrabec at suse dot cz 2006-04-11 09:38 ------- > OK. But current week start data are broken for sure, too. > > Please let me know, whether glibc will plan to use "week_start" or ISO 14652 > "week" lines. I will try to contact translators and ask them for confirmation > (actually I have more issues to collect from them - preferred setup of LANGUAGE > variable, missing transliteration support in locales,...). I am also interested in tidying up the data. If I can be of help, please contact me. > --- > > We searched over all our distribution, and it seems, that no package actually > uses it: util-linux's cal has this part commented out (because it gave bad > results), upstream gtk+ uses glibc week start, but most distributions patch gtk+ > to not use these data (and use po filess fallbacks) or patch glibc to fix these > data (because they got complains). > > Our based on gtk+ fallbacks in po files are better (and provided by native > speakers), but still not correct, because they are language based, not > language+country based. I am not sure, what is the source of Debian patch, but > we can start by comparing them. The way forward I think is to have the data in good shape, then the sw can begin to use it. best regards keld -- http://sourceware.org/bugzilla/show_bug.cgi?id=2388 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-04-11 20:56 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-23 12:16 [Bug localedata/2388] New: " mmarek at suse dot cz 2006-02-23 12:17 ` [Bug localedata/2388] " mmarek at suse dot cz 2006-02-27 16:14 ` decimal at us dot ibm dot com 2006-02-28 21:01 ` decimal at us dot ibm dot com 2006-02-28 21:08 ` sbrabec at suse dot cz 2006-02-28 21:14 ` sbrabec at suse dot cz 2006-02-28 22:31 ` dsegan at gmx dot net 2006-03-08 22:06 ` barbier at linuxfr dot org 2006-04-07 10:04 ` samuel dot thibault at ens-lyon dot org 2006-04-10 18:19 ` drepper at redhat dot com 2006-04-11 9:38 ` sbrabec at suse dot cz 2006-04-11 20:56 ` keld at dkuug dot dk [this message] 2007-10-14 18:05 ` drepper at redhat dot com [not found] <bug-2388-131@http.sourceware.org/bugzilla/> 2012-03-08 4:42 ` carlos at systemhalted dot org
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=20060411205607.26678.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).