I can't change the start of the week from Monday to Sunday. I'm not discounting something obvious which I've missed but I'd expect to see an option in: settings:configure date and time:data and time but there is no option to set the start of the week!
The first day of the week is now fixed by what Region you choose. Go into systemsettings, select Regional Settings, then Formats and from there you can change your Region. (or "locale") You'd have to change to a Region that has Sunday as the first day of the week. The US has that. In Summary: KOrganizer no longer has any control over this setting. another option is to set your environment variable LC_TIME to en_US.UTF-8
Created attachment 106383 [details] attachment-1754-0.html The problem is that (a) there is no setting for day of the week in the regional setting and (b) I'd like to switch the start of the week to different views without changing the locale each time. The start of the week and the locale obey different rules - the start of the week is a personal / context preference that needs to be set easily in korganizer and the locale is a set of default for the system which cannot be easily changed or overridden. This should be user defined in korganizer - there is nothing wrong with inheriting a system default so long as it can be easily changed. ________________________________ From: Allen Winter <bugzilla_noreply@kde.org> Sent: Wednesday, June 21, 2017 9:19 PM To: dav1dblunk3tt@hotmail.com Subject: [korganizer] [Bug 374803] How to change start of the week from Monday to Sunday? https://bugs.kde.org/show_bug.cgi?id=374803 Allen Winter <winter@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winter@kde.org Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Allen Winter <winter@kde.org> --- The first day of the week is now fixed by what Region you choose. Go into systemsettings, select Regional Settings, then Formats and from there you can change your Region. (or "locale") You'd have to change to a Region that has Sunday as the first day of the week. The US has that. In Summary: KOrganizer no longer has any control over this setting. another option is to set your environment variable LC_TIME to en_US.UTF-8 -- You are receiving this mail because: You reported the bug.
Is this thing dead? Because it looks very ridiculous in countries (such as say, Israel) where they are scarcely aware that a week is not Su-Thu. Could you please help us get an understanding where is the problem? Because, obviously, our regional settings are set appropriately and still the piece of code seems to force itself on everything else? It is quite annoying and reflects a lack of care to quite a few non-us/europe countries in the world
have you tried setting Locale to he_IL or en_LI? I wonder what happens then. I'm not against adding a special first day of week setting in KOrganizer. I can see where if could come in handy for example if you are working remotely for a company that doesn't observe the same locale as you.
we do have the work period checkboxes. I look at using the first day selected there as the first day of the week.
(In reply to Allen Winter from comment #5) > we do have the work period checkboxes. > I look at using the first day selected there as the first day of the week. Of course I tried, the locale is set properly on all my machines, and the work-day checkboxes are not having any effect and actually, revert themselves (to none selected, actually it's quite bizarre) once I ok the Pref window, everytime. The behavior seems extremely buggy. I can state a fair background in multiple programming schemata and feel obliged to make this delineation, but I do greatly appreciate the efforts you guys put into this otherwise interesting application framework with superb potential. Nate
Duplicate of bug 358106?
I agree similar / duplicate issue to bug 358106? Locale and working week boxes do not address the problem.
still no solution to this?
Still can't appear to do this in v5.5.3.
*** This bug has been marked as a duplicate of bug 358106 ***