Author: Gerard.meijssen
Description:
When an event happened and it is known to have happened in a year or month of a different calendar (than the Gregorian), precision is lost of up to 50% when a mapping is to be made to the Gregorian calendar as is now the default.
Please support dates in any calendar.
Thanks,
GerardM
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | hoo | T61766 Support for months and years of a different calendar | |||
| Open | None | T59930 Representation of time inside TimeValue objects should depend on the calendar model | |||
| Open | None | T126445 Allow selection of value parser, validator, and formatter to depend on the data value itself. |
[The bug title does not describe a bug but a solution or feature / new functionality. Hence setting priority to enhancement.]
precision is lost of up to 50%
Any example? I fear I don't understand so far.
Gerard.meijssen wrote:
The lunar year starts depending on the cycles of the moon. Consequently there is no relation to solar based months. The Solar Hijira starts with the spring equinox and its months have their own lengths (not the same lengths as months in the Gregorian months...
Thanks,
GerardM
Wikibase Database is not even deployed. Bug misplaced. Please post time issues here https://github.com/DataValues/Time/issues