Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103288 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 83635 invoked from network); 30 Sep 2018 21:25:26 -0000 Received: from unknown (HELO mout.gmx.net) (212.227.15.18) by pb1.pair.com with SMTP; 30 Sep 2018 21:25:26 -0000 Received: from [192.168.2.136] ([91.8.166.159]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Mb8MV-1gQnzc1559-00Ke5Z; Sun, 30 Sep 2018 19:34:35 +0200 Received: from [192.168.2.136] ([91.8.166.159]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Mb8MV-1gQnzc1559-00Ke5Z; Sun, 30 Sep 2018 19:34:35 +0200 To: Kurt Weber , internals@lists.php.net References: Message-ID: Date: Sun, 30 Sep 2018 19:34:35 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:NB6zuf+P7ZWuSPepl2SWiFvqrw+/WTQhcgwxSE+vAKy+IpAHkfB dAO/xOsnTtKLlojDIuvweArJ2pL7HfAuIJwEpHMr8tLCTtLL0C6La6jYzlWgVfMV03Y/w2v D5xaWCv/BhCEQVzeWnBA9Z/kKJD2mBOeLfvG47mTU3GAIsZvY6z7dJTmEaon++dK6lSuboY KZ7RNm7S/bLXtgS8xBj2w== X-UI-Out-Filterresults: notjunk:1;V01:K0:ewFa7/jSB/c=:PyOXGxV77BFlCQluA930LH WhbLFs9MLKDaMrTzs1nte/IynP63IcP8EAhTPiPgukfnly1THAg8SPTb61Uih+JliHrzTcMzL tXrTjrYusZt/Z10irzceHlMDh3KaP7m9vdKrigZmQhkBkmMef1BAjm1GuyAmMaHK+L74zXltV kkraW/9ZGfHljNLA7IBDKP3/StuYCw5/FEpQN2tzC2BQ9GOPJg6JSmpptLuh1g5zLA41Rok6B 5pyY+aRtnJXVJpj9FaQZap/yuVifPWjT84GupxZPMieKem9bf7xgbcmrF8SmW3gEQWIoWvb+d xoLfZI/TvcKxtBUy9BW8eKliFADmv6APf/Z5zWQNb4ep9ohL3Bb1d6yl7t4yJpxCQTxR3l4oh lbE3ylRIPaljm41JXM1EJqWImtx8+0J3VxZQLD9cqlUjsFde8QiuRcFw45+dIWLGdENhSBpOJ QCZ5r6PrHVjSEptGzUKiUxAInrEcxjFxI0pqvTu5/Dk77llg1KyTi2T8s7E9KB+wFjJuW645u ltG0De2RXiajHoVb4Q67g46ea8ln5EE8fIDZeJq0O5HJ2Xzh02ZmTqZDTlNwa9ITeWdcgR6q3 A9V48/7Y4mIEhAqS9YOq2WEAKze1BNstQKcexHzvGfT5hjLkmCR+YXYQI0OzVIsf5s0zsvHI6 D3M9mJbOXG4kCNLfJsk5jST029cAR6yx++FKKiTCSz897rSsOzD3V25Oql4HSTUBF7JetE8UV A+7T6LX9SgVl5yq95EEwcpSRj24q75DMrG3QV3Hy+X5SXhvbXXL9JB9ctvd1kbDFanj6bpBWz NZOXv9oD9fy0Fr6L0hn5wOS3f7shKzVRZo0nnn9IYGYg5LmGl4= Subject: Re: Proposal: Add tabular Islamic calendar to calendar conversion functions From: cmbecker69@gmx.de ("Christoph M. Becker") On 29.09.2018 at 02:27, Kurt Weber wrote: > Gah, I had my filter for this mailing list misconfigured and so I just > now saw this. So so so sorry. > > I'll definitely do a RFC. Great! I you have not already, you can register as Wiki user via . Please send a notice regarding your user name, so that one of the Wiki admins can grant you RFC karma. > Regarding issue (c), I'm obviously not > familiar with internal PHP development processes, but is it usually > the case that "You have X similar thing" is an argument for doing Y? > Seems like there's no reason these decisions couldn't be made on an ad > hoc basis--tabular calender is one thing because it's entirely > self-contained, while other calendars would require access to an > external data source that may disappear at any time, etc. Yes, if in doubt these decisions will be made on a case-by-case basis, but I think it's useful to add the argument about not needing any external data source to the RFC. > On Sat, Sep 1, 2018 at 5:09 AM, Christoph M. Becker wrote: >> On 30.08.2018 at 22:33, Kurt Weber wrote: >> >>> The calendar conversion functions currently support (via Julian Day >>> Numbers as an intermediary) conversion between Gregorian, Julian, >>> Hebrew, and French Revolutionary calendars. Conspicuously absent is >>> the Islamic calendar. A comment in ext/calendar/sdncal.h seems to >>> suggest that the original author(s) intended to implement at some >>> point, but never got around to it. >>> >>> The Islamic calendar offers some complications because in most >>> places and communities that use it for religious purposes, the switch >>> from one month to the next is based on actually observing the moon in >>> the proper phase. In theory the date of this change can be >>> calculated (and indeed the early Islamic surge in study of astronomy >>> was motivated by the wish to know about when they should start >>> looking), but tradition still demands that it be actually observed >>> before a change is made--the actual impact of this is that local sky >>> or weather conditions can sometimes interfere with the observation in >>> a particular jurisdiction, meaning that often it comes a day or so >>> later than when it otherwise would. >>> >>> Consequently, what I'm proposing is the Tabular Islamic Calendar, >>> which was specifically created to be predictable and calculable. It >>> is of limited use for religious purposes (and documentation should >>> probably be clear about this), but it would be useful for, e.g. >>> people working with historical documents from Islamic communities or >>> groups (In fact, this is how I came to this problem--I am working on >>> a Ph.D. in Russian history, and as a side project I'm developing a >>> PHP-backed website to manage research notes and other information; >>> because I work on prerevolutionary Russia I'm very familiar with the >>> issue of needing to convert between calendar systems (in my case, >>> Julian and Gregorian), and my colleagues working on Islamic history >>> often have similar issues.). >>> >>> Tabular Islamic calendar is not ideal, but it seems like the only >>> realistic option for automated conversion. >>> >>> As far as implementation goes, I could do it. I've already >>> implemented conversion one way, before I stopped work in case there >>> were issues that come up in this discussion that I hadn't foreseen >>> (unfortunately, that happened roughly at the time the mailing list >>> server seems to have died, so it's been paused for a couple of >>> weeks). So all I'd have to do is the other direction, and it'd be >>> ready to test. >> >> Thanks! I'm not opposed to this suggestion. There is the suspended >> feature request #27453[1], and I agree that even a tabular Islamic >> calendar would be much more useful than the French Revolunationary calendar. >> >> Presently, I see three counter-arguments: >> >> (a) already supported by ext/intl >> (b) maintenance burden >> (c) opening up a can of worms >> >> Ad (a): Islamic calendars are already supported by the >> intl extension[2]. Even though ext/intl supports an Islamic calendar, >> that doesn't prohibit that ext/calendar also does, though, since they >> are independent extensions (cf. ext/mbstring, ext/iconv, ext/recode). >> >> Ad (b): if nobody else is willing to step up as maintainer of >> ext/calendar[3], I'd be willing to do so. I've already did some >> maintenance[4] so far. >> >> Ad (c): this is somewhat of a problem. I can easily imagine folks >> requesting support for specific Islamic calendars which would require >> (up-to-date) data, what could easily blow ext/calendar out of >> proportion. Also I can imagine people coming up with “the FOO calendar >> is used more widely than the tabular Islamic calendar, so it should be >> supported as well” argument. >> >> Especially due to (c) I suggest to go through the RFC process[5], >> whereby the RFC could also set some precendence/rules for potentially >> further calendar systems (i.e. what ext/calendar may support, and what not). >> >> [1] >> [2] >> >> [3] >> >> [4] >> >> [5] >> >> -- >> Christoph M. Becker