Bug 115573 - better support for lunar based calendars
Summary: better support for lunar based calendars
Status: RESOLVED DUPLICATE of bug 429892
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdecore (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: John Layt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-02 22:08 UTC by Diego Iastrubni
Modified: 2022-02-09 14:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Iastrubni 2005-11-02 22:08:49 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

As you know, KDE 3.2 (and newer) have support for some calendars based other then the traditional one which is used on *nix.

Some of those calendar systems,  are based on the moon. On those systems, the date changes when the night start (the moon raises) and not on 23:59:59. 

I propose that on lunar based calendars, the KDE system will report the next day, if the hour is above....

This is the point I am not sure of. We do not really have a way of knowing when the day ends. A dirty solution, is asking the user by providing him an input box in which we as for the time when the sun sets down. A sane default, could be 18:30, and people who really follow this issues, will be able to update it manually on a daily basis (or weekly, but that's not out problem any more).
Comment 1 Thiago Macieira 2005-11-03 03:20:10 UTC
Code is appreciated.
Comment 2 John Layt 2008-10-16 21:33:39 UTC
Improved support for lunar calendars (Hijri, Jalali, Chinese, etc) are on my plan for 4.3.  First step will be to borrow code from the KStars guys for the required lunar calculations, get the users location either manually or using GeoClue, and we should then have something workable after that.

Assign to myself for long-term action.
Comment 3 Fushan Wen 2022-02-09 14:14:24 UTC
Moved to 429892

*** This bug has been marked as a duplicate of bug 429892 ***