Your comments

Hi, thanks for using Hebcal.


There is no 30th of Cheshvan in the year 5784. The month of Chesvhan sometimes has 29 day and sometimes 30 days. During the year 5784, Cheshvan has only 29 days.

https://www.britannica.com/topic/Jewish-religious-year#ref34905

Thanks! That's helpful.

We will plan to implement this feature. Based on what you describe, following the same rules for birthday/anniversary could work fine. The rules for yahrzeit are more complicated because they depend not only on the Hebrew date of the event itself, but also on the character of the year that the 1st anniversary occurs in... Given some of the examples you listed, those special yahrzeit rules wouldn't apply.

For now, "Anniversary" is the closest match to an "Other" category. When we add the feature we will be sure to update this ticket. You will be able to log into any existing calendars you have and simply switch the event type and the title will be simplified to include only the text you entered on the Hebcal page (with optional Hebrew date appended, if you checked that checkbox).

Hi, thanks for using Hebcal, and thanks so much for your feedback.

Can you please say more about how you're trying to use the Yahrzeit + Anniversary calendar? What kind of events are you trying to schedule that aren't a yahrzeit, birthday or Hebrew anniversary? We would like to understand more about the specific use case of recurring events on the Hebrew calendar to see how to properly design an "other" category. If we do create an "other" category, we could remove the year calculation (1st, 2nd, 3rd, 4th, ...) from the event title.

For edge cases for events that occur on the 30th day of Cheshvan, Kislev, or Adar I in years where that day does not occur. Since they are Rosh Chodesh, presumably they should be postponed to the 1st of the following month (following the same rule as special cases for birthdays).

Mo'adim L'Simcha!

Thanks for the clarification about the intended use case. Knowing that it's for IFTTT, we may be able to do this faster by accepting a URL parameter like yomTovOnly=1 at the end of the iCalendar URL. It vastly simplifies our implementation when there is no user interface required. It would require hand-editing the Hebcal download URL to append the correct suffix, but generally IFTTT users are comfortable with that kind of editing.

Thanks! You can send to mradwin@hebcal.com

We probably won't be able to begin implementing this until after Pesach. You can go ahead and send the document as soon as you're ready and we'll find some time to take a quick look to give you some feedback.

Great! That would definitely help.

Shabbat shalom!

Great suggestion! We've added a dedicated calendar feed for this.

https://www.hebcal.com/ical/

Image 219

Thank you for pointing to those sources.

Regrettably, my Hebrew is very weak and I probably won't be able to utilize those sources without some assistance. Would you be willing to prepare a spreadsheet to help out?

If you were able to create something like this (using the example from pages 251-253), this would probably be sufficient to code up a perpetual calendar feed.

Simple YearLeap YearSectionRules
30 Cheshvan, 29 Adar, 29 Tammuz2 Kislev, 11 Adar II, 21 Tammuzהלכות לשון הרע7:7-7:8

If I understand the layout of the book correctly, the corresponding pages in Sefaria for those dates above would be these:

Part One, The Prohibition Against Lashon Hara, Principle 7, Seif 7

Part One, The Prohibition Against Lashon Hara, Principle 7, Seif 8

Hi, thanks for using Hebcal, and thanks for your message.

We're not quite sure what you mean the "entre and exit of Sabbath are the same".

If you use the Hebcal iCalendar feeds and you specify a location for candle-lighting times, you will see an event called "Candle lighting" on Friday night to indicate the beginning of Shabbat and an event called "Havdalah" on Saturday night to indicate the conclusion of Shabbat. These events are typically approximately 25 hours apart, so they are not at the same time. 


You may notice that the aforementioned "Candle lighting" and "Havdalah" calendar events have 0-minute duration. For example, if the start time is at 17:49pm the the end time of that event is also at 17:49pm. Unlike a calendar appointment which might have a 30- or 60-minute duration (which would indicate a range of times), these events deliberately have a 0-minute duration to indicate a moment in time. They are designed to serve as a reminder.


Does this answer your question?