Your comments
Note that there appears to be a limitation in Android calendar where events more than one year in the future will NOT sync to your device. The events are visible on the Google Calendar on the Web but will not download to the device until the current date approaches more closely.
See these articles for more detail:
How do I sync Google Calendar events that occur more than one year in the future?
Triennial readings are already posted on the bottom of each parasha page if they differ in future cycles. Scroll down to the bottom of a parasha page and look for "Triennial readings for previous and future cycles".
In addition, you can also download triennial leyning schedules for 10 years into the future in CSV format here:
at the bottom of the page you will see something that says
Triennial readings for previous and future cycles
Thanks for this suggestion. We will look into implementing something similar.
Hello, thanks for using Hebcal. The 11 of Sivan begins Thursday night at sundown, and the majority of 11 Sivan is in fact on Friday.
https://www.hebcal.com/converter/?hd=11&hm=Sivan&hy=5779&h2g=1
Hello, thanks for using Hebcal!
We have added documentation for the lg= parameter to this API:
Hi, thanks for using Hebcal!
We don't see the error - could you explain which day in May or June is incorrectly shown as ניסן when in fact it's supposed to be סיון
Thanks for the clarification. You can definitely use this API to get exactly what you want. Just specify nx=off&nh=off&s=on
We don't appreciate this negative and corrosive language.
Hebcal is free software. Please take your business elsewhere.
Customer support service by UserEcho
Note that there appears to be a limitation in Android calendar where events more than one year in the future will NOT sync to your device. The events are visible on the Google Calendar on the Web but will not download to the device until the current date approaches more closely.
See these articles for more detail:
How do I sync Google Calendar events that occur more than one year in the future?
Android Bug #41281