The Strange Mystery of the Vanishing Polish S

By Aresluna Marcin Wichary
Originally published in Medium Engineering (February 2, 2015)

A few weeks ago, a user reached out to the Medium team with a peculiar report:

“I just started an article in Polish. [And a specific character keeps disappearing.]”

At first glance, this seemed inexplicable. Our system doesn't implement any language-specific logic or "special-casing." Even if we did, it defied logic: out of the 32 distinct characters in the Polish alphabet, why would only one specific letter be problematic?

This is the chronicle of how four unrelated factors, spanning decades—and perhaps centuries—converged to create a bizarre technical glitch, and the process we used to resolve it.

---

🧩 The Ingredients of a Bug

To understand the "Vanishing S," we have to look at the components that built the problem.

• Ingredient 1: The Polish Language
• Ingredient 2: The Era of Communism
• Ingredient 3: Deep-seated Muscle Memory
• Ingredient 4: (The final piece of the puzzle)

Ingredient 1/4: The Polish Language

Polish is a Slavic language, ranking second in usage behind Russian and ahead of Ukrainian. Unlike those two, Polish utilizes the Latin/English alphabet as its foundation, though it adds its own unique flair.

The Alphabetical Breakdown:

• Standard Latin: The base alphabet is largely identical to English.
• Excluded Letters: Original Polish words typically avoid Q, V, and X (though they appear in loanwords).
• The Additions: To replace those, Polish incorporates nine specific diacritics based on Latin characters.

In the early 1900s, typewriter manufacturers had to adapt to these nine extra letters. If you compared a US typewriter to a Polish one, you'd notice that Ł and Ż were given their own dedicated keys, while others were tucked away, sharing space with numbers.

Typists simply had the keys they needed. In reality, to create uppercase versions of some letters, typists had to perform a manual "hack": type the base letter, backspace, and then strike an accent key to simulate the correct character. To make room for this, punctuation like semicolons and parentheses were often sacrificed or replaced by combinations (e.g., a comma + backspace + colon).

Ingredient 2/4: Communism

For those exploring 1980s computing, the political climate of Poland under Communism created two major hurdles:

1. Financial Constraints: Very little disposable income for the average citizen.
2. Trade Restrictions: Commercial imports of Western technology were forbidden (though individuals could occasionally smuggle them in if they had the foreign currency).

The author's first machine, the Atari 800XL, was based on 1979 tech but repackaged in 1983. Because of the Iron Curtain, technology arrived late and without localization. There were no companies authorized to "Polish-ize" these machines.

Consequently, computers arrived with American keyboards. While countries like Germany (QWERTZ) or France (AZERTY) received customized hardware, Poles had to improvise.

The Linguistic Stakes: While these diacritics only make up about $8\%$ of letter distribution—calculated roughly as: $\text{Frequency} \approx \frac{\text{Diacritic Count}}{\text{Total Characters}} \approx 0.08$ ...they are vital for meaning. Changing one accent can completely alter a sentence's meaning.

The Solution: The "Programmer's Layout" Since hardware modification was impossible, users turned to modifier keys: Ctrl and Alt. Because Ctrl was already used for shortcuts, a standard emerged: use Alt to access the nine diacritics.

This created two distinct schools of input:

• The Typist's Layout: Mirrored old typewriters (required specific hardware).
• The Programmer's Layout: Used Alt modifiers on a US keyboard.

The "Programmer's Layout" won out because it preserved the punctuation symbols essential for coding. Despite being an ergonomic disaster—requiring the left hand to stretch awkwardly toward the Alt key—it became the dominant standard, much like the suboptimal QWERTY layout.

Ingredient 3/4: Old Habits Dying Hard

In the 80s and 90s, "autosave" didn't exist. Saving a file was a resource-heavy process:

• Mechanical Wear: Floppy drives wore out with every write.
• CPU Lag: The system would often freeze or slow down during a save.
• Risk of Loss: System crashes were frequent and brutal.

As a result, writers developed a psychological tick. Whenever they paused to think, their fingers would instinctively hit Command + S or Ctrl + S.

Ctrl + S became more than a shortcut; it became a motor memory. It was as intrinsic to the act of writing as the fear of the blank page.

However, in a modern web-based editor, pressing the "save" combination often triggers a browser dialogue—a completely useless pop-up that interrupts the flow of writing.

---

Current Status of the Investigation:

• Language analyzed
• Hardware history mapped
• User behavior identified
• Conflict resolution (Pending)