Description of problem: In Switzerland, the first day of the week is monday, not sunday. In /usr/share/i18n/locales/fr_CH, there are missing parameters in LC_TIME: first_weekday 2 first_workday 2 Version-Release number of selected component (if applicable): glibc-common-2.20-8.fc21.x86_64 (also present in f20 and f22) How reproducible: Always Steps to Reproduce: 1. install fedora with fr_CH 2. open clock-applet in mate (by example) Actual results: First day is Sunday, not Monday Expected results: First day is Monday Additional info: After you add the three lines at the end of LC_TIME, to be effective, I had to use: localedef -v -c -i fr_CH -f UTF-8 fr_CH.UTF-8 then, the file: /usr/lib/locale/locale-archive is modified with the new info. If I look bug #624296, I cannot find an official info telling explicitly that monday is the first day of the week.
de_CH, that is in the same country than for fr_CH (Switzerland) has it already (fr_FR, de_DE, etc. have it too) Would it be possible to do it too for fr_CH ?
it_CH doesn't get this change too though. So if it is possible for fr_CH, probably would help to change it for it_CH too :)
Hello, Will the CLDR import that is in glibc master be backported to f23 too ?
(In reply to Heldwin from comment #3) > Hello, > > Will the CLDR import that is in glibc master be backported to f23 too ? No, but we can (and eventually will) fix individual locale issues users report. I want bugs for any such change so that users have a way of finding out what changed and why (“CLDR import” is not very illuminating).
ok, but may I hope this report about fr_CH will be fixed too ? I also don't understand why it was fixed for es_CL (#1321372), and not fr_CH. For reference, for es_CL, it was Reported in 2016-03-25 16:34 EDT for fr_CH, it was reported in 2015-03-22 17:32 EDT so this one was reported about 1 year before. Can you please explain it to me (because the reason is not very illuminating too). Thanks
(In reply to Heldwin from comment #5) > ok, but may I hope this report about fr_CH will be fixed too ? Yes, eventually, probably as part of the next update. > I also don't understand why it was fixed for es_CL (#1321372), and not fr_CH. I picked up bugs in reverse chronological filing order, and had to stop at some point to actually get *some* bug fixes out.
glibc-2.22-16.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b0e67c88b5
glibc-2.23.1-7.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b321728d74
glibc-2.22-16.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b0e67c88b5
glibc-2.23.1-7.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b321728d74
Thanks a lot, the update glibc-2.22-16.fc23 fixes it.
glibc-2.22-16.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
glibc-2.23.1-7.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.