Bug 190065 - korganizer uses italian holidays even if country is set to spain
Summary: korganizer uses italian holidays even if country is set to spain
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-19 13:43 UTC by Davide Bettio
Modified: 2017-01-07 21:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Davide Bettio 2009-04-19 13:43:09 UTC 
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

korganizer uses italian holidays even if country is set to spain.
System Settings - Regional & Language -> Country or region: Spain
Comment 1 Allen Winter 2009-04-19 16:55:23 UTC 
korganizer doesn't look at regional settings for the holidays.  afaik, the user needs to go into korganizer settings->Time&Date page and set the holiday region there.
Comment 2 John Layt 2010-05-29 02:31:16 UTC 
Auto-default of holiday region is a good idea in say the plasma calendar (where it has been implemented for SC 4.5) but is probably not so good in KOrganizer where users may not want holidays displayed, or may want a different region displayed than their locale.  And changing a users chosen region setting is not good if they really want the old region.  One way would be to add "Use Locale" as an option on the region list which would then follow any locale changes.  I'll ponder that for 4.6.
Comment 3 Denis Kurz 2016-09-24 18:48:16 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:25:44 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.