The Hidden History Behind Šāpšu
Behind the modern ASCII shapash hides a longer story. The name is attested in Phoenician as 𐤔𐤐𐤔. Etymologically it means "The sun". The ASCII form shapash survives only because the early domain-name system could not carry diacritics; it is a technological compromise, not an ancient spelling. The Unicode restoration Šāpšu recovers the vowel length of the original directly in the address bar. The original preserves one prosodic feature — stress or vowel length — rather than both, which places the name in Tier 2. The letter-by-letter transformation runs: - s → Š — Special character - h → — — Dropped - a → ā — Long vowel - p → p — Same - a → š — Special character - s → u — Special character - h → — — Dropped The project holds the domain šāpšu.com (xn--pu-cla79ac.com) as the canonical home of this name. That history reaches back through manuscripts, inscriptions, and oral traditions before it ever reached a keyboard.
Etymology
The deeper roots of Šāpšu are still debated among specialists. The traditional gloss is "The sun."
In Myth
Šāpshu's mythology is woven through the Baal Cycle and Ugaritic ritual texts. She does not fight like Anat or Baal; she illuminates, witnesses, and transmits divine will. Her descent into the underworld marks the boundary between day and night, life and death. These narratives are not dusty footnotes; they are the reason the name acquired its resonance.
Across Cultures
Šāpshu corresponds to the Mesopotamian Shamash and the later Aramaic/Achaemenid Mithra as a solar deity of justice and oath. She also overlaps with the Egyptian Hathor in her role as a cow or sun-goddess who guides the dead. In the Hebrew Bible, the common noun šemeš ('sun') is never personified as a goddess, but the Ugaritic evidence shows that Northwest Semitic peoples once knew the sun as female. The winged sun disk of Phoenician and Israelite iconography may carry echoes of her protective radiance. Kindred figures in the PÚNYCODEX cross-tradition index include [[apollon|Apóllōn]], [[dazhbog|Dažbog]], [[helios|Hēlios]], [[huitzilopochtli|Huitzilopōchtli]], [[ra|Rꜥ]], and [[shamash|Šamaš]], each linked through sun / light. Names travel, adapt, and accumulate meanings. Tracking that travel is part of what makes the restoration worthwhile.
The Unicode Decision
Restoring Šāpšu is not an aesthetic choice. It is a decision to honor the name as attested rather than the name as flattened by ASCII. That choice is documented in the Scholarly Edition and defended by the sources below.
Why This Restoration Matters
Restoring Šāpšu is part of a larger effort to make the web multilingual by default. The PÚNYCODEX project does not ask users to learn a new alphabet; it asks the infrastructure to respect the alphabets that already exist. A single Unicode domain is a small proof, but it is a proof that scales: every name restored makes the next one easier.
Related Names
Sources
The Cultural Afterlife
Her name survived by becoming a noun. Hebrew šemeš is simply 'the sun' — grammatically feminine, like the Ugaritic goddess, but emptied of cult; the biblical polemics against sun worship are intelligible only because the cult existed, as Josiah's removal of the sun-horses and Ezekiel's vision of men bowing eastward at the temple attest. The imagery refused to stay buried: Malachi's promise of a 'sun of righteousness' rising 'with healing in its wings' (Malachi 4:2) — itself an heir of the winged solar disk — was read by the church fathers as a prophecy of Christ, carrying West Semitic solar theology into Christian liturgy and art. In modern scholarship Šāpšu has become a case study in the variety of ancient solar religion: she can appear as...
The PÚNYCODEX Angle
The PÚNYCODEX project treats Šāpšu as more than a curiosity. It is a proof that the domain-name system can carry the full weight of human naming, from Phoenician to the modern browser. Every visit to this temple is a small act of preservation.
For Developers and Linguists
The PÚNYCODEX dataset exposes Šāpšu through a versioned API, making the restoration usable by search engines, localization pipelines, and scholarly tools. Because the canonical sources are stored as structured JSON, every improvement flows automatically to the temple, the extension, and the mobile app.