hebcal
Korach Hebrew spelling
In the vast majority of locations קרח is spelled without the vuv. (Notably the first Pasuk in the Parsha). Would suggest adjusting קורח to קרח
- https://www.sefaria.org/Numbers.16.1-18.32?lang=he&aliyot=0
Thanks for taking the time to write to us.
In many places Hebcal renders Hebrew text without nikkud. When the vuv is missing, it is easily read as קֶרַח which has an entirely different meaning. I believe this was the original intent for why we chose the spelling with the vuv, knowing well that it differs from how the name appears in the Torah.
@dsadinoff do you have an opinion here? I am not knowledgeable enough of a Hebrew speaker to be able to offer a good argument either way.
FWIW, my vote would be to keep the vov. Shas is full of references to cholams that way when there's no nikud. And, in Modern Hebrew, you will find it a lot, e.g. Wikipedia.
That said, I originally wrote "you'd almost always find", but when I searched it just now I realized that I'm wrong. It may be subjective. I think that context is also significant--if you already wrote "Parshas" then it is clear what you mean.
context is also significant
Sums up my thoughts. For an API that lists Parshas I think it would be safer to assume the context will typically be Parsha-centric. (In my case, and I'm sure I'm not alone, I'm generating Shul davening times so I would expect the Parsha name to be consistent)
Even in my own example (Wiki), they do remove the vav when written with Parshat: Wiki. So yes @Abba- it makes sense.
Hey its another year and another Shul calendar needed manual fixing! (gasp! /s) Just checking in on this :)
OK, we're rolling out a change to use קֹרַח with niqqud and קורח without. This change applies to the hebcal.com website for now, and will eventually also be in the Hebcal CLI
@mjradwin Thanks!
Which would the web API fall under? (i.e. https://www.hebcal.com/hebcal?cfg=json.....) for the "hebrew" element.
The CLI is separate. The API should be updated
https://www.hebcal.com/hebcal?cfg=json&v=1&s=on&leyning=off&year=2025&month=6&lg=he
{"title":"פָּרָשַׁת קֹרַח","date":"2025-06-28","hdate":"2 Tamuz 5785","category":"parashat","title_orig":"Parashat Korach","hebrew":"פרשת קורח","link":"https://hebcal.com/s/5785/38?us=js&um=api"}
Based on @YizYah's comments, Can I ask you to consider updating this either for the "hebrew" field specifically, or maybe decide by when the context is with the "פרשת"? I use the english language option...
As YizYah noted, in this case where it's obviously the Parsha context as thats part of the "hebrew" value (and the field is literally hebrew) I think users would expect to see the original spelling.
(https://www.hebcal.com/hebcal?cfg=json&sec=1&tzid=America/New_York&F=on&lg=a&s=on&ss=on&mf=on&nx=on&min=on&maj=on&o=on&start=2025-06-28&end=2025-06-28)
{ "title" : "Parshas Korach", "date" : "2025-06-28", "hdate" : "2 Tamuz 5785", "category" : "parashat", "title_orig" : "Parashat Korach", "hebrew" : "פרשת קורח", ...
Use &lg=he as described above to see the version without the vav.
We use קֹרַח with niqqud and קורח without
Yes but that was part of this whole discussion is doing that when the Parsha context is present.
Our API usage has been around a while already with english, so would seem counterproductive to call the bulk API twice just to merge in the 'correct' hebrew parsha spelling.
(And to clear appreciate the time either way, hebcal is an amazing resource 🙂)