Fix Tanya Yomi 11 Iyar (Peshuta): start at Likkutei Amarim 46:6, not 46:8 - #185
Open
meirpro wants to merge 1 commit into
Open
Fix Tanya Yomi 11 Iyar (Peshuta): start at Likkutei Amarim 46:6, not 46:8#185meirpro wants to merge 1 commit into
meirpro wants to merge 1 commit into
Conversation
…ad of 46:8 The printed Kehot Chabad Tanya Yomi calendar (chabad.org/dailystudy/tanya.htm) starts 11 Iyar in a regular year at the 'Asher Kidshanu Bemitzvotav' passage, which corresponds to Sefaria's segment 46:6 — not 46:8 as in the current CSV. This means today's CSV currently makes 10 Iyar (which auto-derives its end from the next day's start) span 46:4-7 instead of the printed 46:4-5, showing two extra segments that belong to 11 Iyar. Four rows are affected — every regular-year (non-leap) 11 Iyar in the file: - 5/2/2023, 5/9/2025, 4/28/2026, 5/7/2028 No 10 Iyar rows need to change because the CSV records only the starting segment per day; downstream consumers compute the range from consecutive starts, so shifting 11 Iyar's start back by 2 segments fixes both days.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fixes the start of 11 Iyar in the Chabad daily Tanya Yomi schedule for regular (non-leap) years from
Tanya, Part I; Likkutei Amarim 46:8to46:6.Why
The printed Kehot Chabad Tanya Yomi calendar — what chabad.org/dailystudy/tanya.htm follows — starts 11 Iyar in a regular year at the "אֲשֶׁר קִדְּשָׁנוּ בְּמִצְוֹתָיו" passage, which corresponds to Sefaria's segment 46:6, not 46:8.
The downstream effect today: consumers that derive each day's end segment from the next day's start (the standard pattern for this CSV) compute 10 Iyar Peshuta as
46:4-7(4 segments) when the printed shiur is46:4-5(2 segments). Two segments end up duplicated on 10 Iyar that actually belong to 11 Iyar.This was caught by users of an external app (HaYom Daily Study, hayom.app) cross-referencing chabad.org's daily Tanya page.
Verification
…וּלְבוּשֵׁיהֶן הַנִּזְכָּרִים לְעֵיל – בְּאוֹר־אֵין־סוֹף בָּרוּךְ־הוּא.(Sefaria segment 46:5).וְזֶהוּ שֶׁאוֹמְרִים: "אֲשֶׁר קִדְּשָׁנוּ בְּמִצְוֹתָיו"…(Sefaria segment 46:6).<i data-overlay="Vilna Pages" data-value="[פ: יא אייר]">marker currently sits at segment 46:8 — that marker should also move to 46:6 for internal consistency, but this PR only patches the CSV (the marker placement is a separate concern inSefaria/Sefaria-Export/Sefaria-Project).Scope
Four rows changed — every regular-year 11 Iyar entry in the file:
5/2/2023,יא אייר,11 Iyar46:846:65/9/2025,יא אייר,11 Iyar46:846:64/28/2026,יא אייר,11 Iyar46:846:65/7/2028,יא אייר,11 Iyar46:846:6No 10 Iyar rows are touched — the CSV records only the starting segment per day, so shifting 11 Iyar's start back by 2 segments correctly fixes both days at once.
Leap-year rows (
9-19 → 9-18cycle, including 11 Iyar) are intentionally untouched — they have a different segmentation per the מ-edition markers in Sefaria's text and were not verified against the printed calendar in this report.