As you may know, the U.S. is changing the Daylight Saving Time rules this year due to the Energy Policy Act of 2005. The server currently hosting this site does not yet have the Java patch for this. This means that from the second Sunday in March (the 11th) until the the last Sunday in March (the 25th), calendars generated from the Zmanim Calendar Generator will show the zmanim in standard time and not daylight savings time (DST). The same issue will happen in the fall from the last Sunday in October (the 28th) till the first Sunday in November (the 4th). The Java version used by the server should be patched within the next week or 2 to the latest Java 5 (JDK 1.5) version to solve this problem.
The Hebrew date Plugin has not been in active development for a while, and I am pleased to announce that it now has a new home at mikeage.net. Mike added a config page as well as a few new options. The plugin can be downloaded from the WordPress Hebrew dates Plugin Page. As a backup, you can also download it from Mike’s Site (zip). In addition to Mike’s work, Jacob Fresco has used the code to create an additional Jewish Date plugin that displays the current Jewish date. This plugin has since been merged to Mike’s version.
Read the following posts at Mike’s site for more details
The first phase of change to allow easier porting to other languages took place with the change in the API from using inheritance of the Java Calendar classes, to one that uses composition. This will make porting it to other languages easier. Included in the update are a number of new zmanim, mostly the addition of a number of new calculations for plag that are useful when trying to avoid a tartai desasri with early erev shabbos minyanim.
The Zmanim Calendar Generator now has a simple way to look up longitude and latitude information using the Google Maps API. To use this feature, click on the Google Maps icon to display the map (location centered on Bais Medrash Gevoha in Lakewood), find the location that you want to generate zmanim for, and click that point in the map. This will update the longitude and latitude fields in the form. The Google API was pretty straight forward and simple. At the same time I tried to integrate an elevation lookup. Google does not provide elevation information, but I attempted to look it up using a webservice. This seemingly simple task was not very straight forward. The approach was to grab the SOAP response from the REST style elevation webservice made available by Jonathan Stott. My plan was to do this all via the client sided XML parsing. The first issue encountered was browser security that does not allow cross-domain loading of XML documents (By the way this was not using XMLHttpRequest, but the same security restrictions apply). This was solved by a simple PHP page that was just a proxy for the call. That done, I managed to get it to work in IE, but it crashed the browser every second call or so. The crashing was solved by adding a small delay. I never managed to get it working in Mozilla. I later tried to use the existing Google Maps API to load it, but never got it working. I commented out all elevation code, and will get to that part at some future date. I also removed the non decimal longitude and latitude option. I hope this will be useful.