Hi, thanks for using Hebcal!

The date May 26, 2023 is a Friday (not Saturday).

On our Parashat ha-Shavua by Hebrew year - Israel - 5783 web page, the following information is displayed:

Shavuot / שָׁבוּעוֹת

Friday, May 26, 2023 · 6 Sivan

Exodus 19:1-20:23; Numbers 28:26-31

Haftarah: Ezekiel 1:1-28, 3:12

This information is accurate. Shavuot for Hebrew Year 5783 begins in Israel at sundown on Thursday, 25 May 2023 and ends at nightfall on Friday, 26 May 2023.

The Torah reading for Shavuot is during the daytime, so it is read on Friday, May 26, 2023, which corresponds to the 6th of Sivan.

On our Parashat ha-Shavua by Hebrew year - Diaspora - 5783 web page, the following information is displayed:

Shavuot I / שָׁבוּעוֹת א׳

Friday, May 26, 2023 · 6 Sivan

Exodus 19:1-20:23; Numbers 28:26-31

Haftarah: Ezekiel 1:1-28, 3:12

Shavuot II (on Shabbat) / שָׁבוּעוֹת יוֹם ב׳ (בְּשַׁבָּת)

Saturday, May 27, 2023 · 7 Sivan

Deuteronomy 14:22-16:17; Numbers 28:26-31

Haftarah: Habakkuk 3:1-19

Does this answer your question?

Hi, we've started work on this and have a beta version available now on the Hebcal.com website. If you visit the Yahrzeit + Anniversary calendar, you'll now be able to pick "Other" in addition to Yahrzeit, Birthday, and Anniversary. If you pick "Other", it's treated mostly the same as Anniversary, but without any modifications to the title.

OK, we've started working on this and have a partially-working version. Open this page and scroll down towards the bottom for the Daily Chofetz Chaim calendar feed:

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

There's at least one known problem for the last day of learning Hakdamah where the text doesn't seem to line up correctly with Sefaria's layout. It's possible it's actually an error on Sefaria's side - more investigation needed.

Hi, thanks for using Hebcal.

Depending on what options you selected when you downloaded the Hebcal calendar, you may find days where there are no holidays. For example, if you didn't check the "Major holidays" checkbox, your calendar may not contain holidays such as Passover. Could you send the full URL you used for your calendar feed (starting with http://download.hebcal.com/ so we can take a look)?

Depending on what calendar program you use, you may find that it's easy to unsubscribe from the calendar and resubscribe with the options that you prefer.

We provide step-by-step instructions for importing into Apple, Google, Outlook and other calendar apps.

Hi, thanks for using Hebcal.

We corrected the error in the Torah reading for third day of Chol Hamoed falling on Monday on 26 January 2023. If you downloaded the 5783 spreadsheet before this date, it contained the incorrect reading.

If you downloaded the 5783 spreadsheet after 26 January 2023, you will see the correct reading in that .csv file:

"Date","Parashah","Aliyah","Reading","Verses"

10-Apr-2023,"Pesach Chol ha-Moed Day 3 on Monday",1,"Exodus 22:24-22:26",3

10-Apr-2023,"Pesach Chol ha-Moed Day 3 on Monday",2,"Exodus 22:27-23:5",9

10-Apr-2023,"Pesach Chol ha-Moed Day 3 on Monday",3,"Exodus 23:6-23:19",14

10-Apr-2023,"Pesach Chol ha-Moed Day 3 on Monday",4,"Numbers 28:19-28:25",7

We apologize for any inconvenience caused.

Hi, thanks for using Hebcal.

If you'd like a compact printable calendar with just the date and weekly Torah portion, you can use our Candle-lighting Times Year at a Glance page for your city.

If you'd like a printable calendar with much more detail, see our Parashat ha-Shavua by Hebrew year pages.

If you'd like a calendar feed with the weekly Torah portion that you can import into Microsoft Outlook, iPhone, iPad, macOS Desktop Calendar, Android (via Google Calendar), or to any desktop program that supports iCalendar (.ics) files, please visit this our simple calendar downloads page and choose either Torah Readings (Diaspora) or פרשת השבוע - ישראל

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.