public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "flyer dot REMOVE dot SPAM at gSmPaAiMl dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/10011] wrong first_weekday/first_workday for de_AT locale Date: Thu, 02 Apr 2009 10:08:00 -0000 [thread overview] Message-ID: <20090402100841.5635.qmail@sourceware.org> (raw) In-Reply-To: <20090329200035.10011.flyer.REMOVE.SPAM@gSmPaAiMl.com> ------- Additional Comments From flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-04-02 10:08 ------- Hello, this bug is taking off in an unwanted direction. This bug is _not_ about correcting the first day of a week in de_AT (which would correspond to week[2]). This bug is about correcting first_weekday (the day calendars should start a week in) in de_AT. Some commentors said, that in Austria weeks are Mondays based (note the difference to first_weekday). This is true. Currently de_AT bases weeks on Sundays. This bug bug however does not address this mismatch. Setting de_AT to Monday based, breaks the output of several applications (date, cal, ...), as for example strftime does not work properly with Monday based weeks. In the end I want to overcome this limitation and base Austrian weeks on Monday. But that's out of scope of this bug. Getting things right requires three steps: 1. Provide a short-term fix to get calendars showing the correct start of a week (This is the purpose of this bug). 2. Correct strftime to treat Monday based weeks nicely (This will become a bug on its own). 3. For countries having Monday based weeks (just as Austria), adapt corresponding locales (This will become other, separate bugs). This bug's sole purpose is to provide a short-term fix for calendars. Let's keep it at that. Kind regards, Paul -- http://sourceware.org/bugzilla/show_bug.cgi?id=10011 ------- 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:[~2009-04-02 10:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-29 20:00 [Bug localedata/10011] New: wrong week/first_weekday/first_workday " flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-03-29 20:01 ` [Bug localedata/10011] " flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-03-30 21:29 ` pasky at suse dot cz 2009-04-01 8:35 ` flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-04-01 8:36 ` [Bug localedata/10011] wrong first_weekday/first_workday " flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-04-01 9:04 ` keld at dkuug dot dk 2009-04-01 17:05 ` tjk at tksoft dot com 2009-04-02 10:08 ` flyer dot REMOVE dot SPAM at gSmPaAiMl dot com [this message] 2009-05-18 5:32 ` flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-05-18 5:34 ` flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-06-15 6:16 ` flyer dot REMOVE dot SPAM at gSmPaAiMl dot com 2009-06-16 15:25 ` drepper at redhat dot com [not found] <bug-10011-131@http.sourceware.org/bugzilla/> 2014-07-01 7:27 ` fweimer at redhat dot com
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=20090402100841.5635.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).