From 0ce1e7d1ba7e325810e83522b941c0cc66938b92 Mon Sep 17 00:00:00 2001 From: Quantum Date: Sun, 20 Jul 2025 22:48:26 -0400 Subject: [PATCH] =?UTF-8?q?mcal:=20explain=20what=20Haab=CA=BC=20years=20a?= =?UTF-8?q?re?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- mcal/public/index.html | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/mcal/public/index.html b/mcal/public/index.html index 3a4de1a..b4db4de 100644 --- a/mcal/public/index.html +++ b/mcal/public/index.html @@ -80,8 +80,8 @@

Since the Haabʼ is the closest equivalent to months in the Mayan system, this calendar application is based on the Haabʼ. This poses a problem, as in the Mayan system, the Long Count is used to track the absolute date and the cycles of Tzolkʼin and Haabʼ are - unnumbered. To mitigate this issue, we attempt to number the Haabʼ cycles, with the date of - creation in cycle 0.

+ unnumbered. To mitigate this issue, I numbered the Haabʼ cycles, with the date of creation in + cycle 0.

@@ -111,6 +111,16 @@ be identified.

+
+
+

How do the Haabʼ years work?

+

In the traditional Mayan calendar, Haabʼ cycles are unnumbered. To help uniquely identify + every screen, I introduced year numbers, with the date of Mayan creation as “year 0.”

+

In my system, the year number increases every time 0 Pop rolls around, with year 0 being defined as the + year containing Mayan creation date (0.0.0.0.0 in the Long Count). This means that creation happens on 8 + Kumkʼu in year 0, and the year continues until 4 Wayebʼ, after which the date is 0 Pop in year 1.

+
+

What's so special about this version?