Bug 9912 - russian-ukrainian weekday wrong
Summary: russian-ukrainian weekday wrong
Status: RESOLVED DUPLICATE of bug 10346
Alias: None
Product: glibc
Classification: Unclassified
Component: localedata (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: GNU C Library Locale Maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-27 17:11 UTC by Clint Adams
Modified: 2014-07-01 20:45 UTC (History)
6 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments
ru_UA week setting patch (269 bytes, patch)
2009-02-27 17:12 UTC, Clint Adams
Details | Diff
Proper patch to fix this problem (250 bytes, patch)
2012-04-04 17:17 UTC, law
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Clint Adams 2009-02-27 17:11:51 UTC
Seems the first day of the week in the Ukraine is Monday.
Comment 1 Clint Adams 2009-02-27 17:12:26 UTC
Created attachment 3781 [details]
ru_UA week setting patch
Comment 2 Petr Baudis 2009-03-03 11:57:28 UTC
Please provide some kind of source/proof or get the locale author to endorse
this change.
Comment 3 Nikita Shulga 2009-03-03 12:15:30 UTC
(In reply to comment #2)
> Please provide some kind of source/proof or get the locale author to endorse
> this change.
Monday is first day of the week in Russian.
And as far as I understand what's written in Ukrainian wikipedia, Monday is first day of the week as well ( 
see http://uk.wikipedia.org/wiki/Òèæäåíü )
Comment 4 Samuel Thibault 2009-03-12 16:12:17 UTC
Please do not change the week value, as this also gives which day the day/abday arrays start. Set first_weekday and first_workday to 2 instead, as detailed in bug 7068 and http://sourceware.org/ml/libc-alpha/2009-01/msg00024.html 
Comment 5 Petr Baudis 2012-04-04 17:02:26 UTC
WAITING for three years now, closing as INVALID.
Comment 6 law 2012-04-04 17:17:34 UTC
Created attachment 6315 [details]
Proper patch to fix this problem
Comment 7 law 2012-04-04 17:18:11 UTC
Please don't close this, it's a valid issue and it's been reported multiple
times into the Fedora & Red Hat databases.  I've researched the issue with
folks in the Ukraine and they've confirmed that glibc is in fact buggy for
their locale.

c#4 AFAIK is the right fix and the one we've been using in Fedora & Red Hat's
releases.  I'm attaching that change.
Comment 8 Petr Baudis 2012-04-04 17:38:22 UTC
Normally, we require the original locale author to agree with the change and/or some kind of verifiable reference on the everyday usage aside of just hearsay - e.g. link to an official material/norm, calendar on some popular (newspaper, etc.) website or something similar.
Comment 9 law 2012-04-04 17:44:31 UTC
I'm quite aware of that.  The lack of response from the locale author says nothing about the validity of a bug.  Given the lack of response from the locale author, someone should seriously look at replacing them as the contact point with someone more responsive.
Comment 10 Dmitry V. Levin 2012-04-04 17:59:58 UTC
(In reply to comment #8)
> Normally, we require the original locale author to agree with the change and/or
> some kind of verifiable reference on the everyday usage aside of just hearsay -
> e.g. link to an official material/norm, calendar on some popular (newspaper,
> etc.) website or something similar.

Please have a look at http://sourceware.org/bugzilla/show_bug.cgi?id=10346
which provides additional information on this issue.

The bug is obvious, the fix is trivial, the locale author is agree.
What else do you need to get the bug fixed?
Comment 11 law 2012-04-04 19:48:51 UTC

*** This bug has been marked as a duplicate of bug 10346 ***
Comment 12 Petr Baudis 2012-04-05 09:33:10 UTC
(Jeff, thanks for handling this; I should have noticed the connection while I was doing triage on both bugs yesterday... Just a note to your comment 9, of course when the original maintainer fails to respond in reasonable timeframe, we proceed without the ack. Perhaps we even want to relax our policies on "proofs" as well, but in that case, someone interested should raise the question on the mailing list.)