Cuneiform Sign Tag

It has no single translation; context chooses the reading.

𒋳 is a reusable sign in Sumero-Akkadian writing: it could write Sumerian words or serve in Akkadian texts. Sumerian, an ancient language of southern Mesopotamia, uses the reading TAG for “to touch”; TAG also has values linked with giving, striking, weaving cloth, and hand or fist. Akkadian scribes could use it as a Sumerian word-sign—a sign standing for a whole word—in place of the Akkadian verb lapātum, “to touch.”

The TAG vs ŠUM question is about readings of the same sign, not two characters competing for one slot. In transcription, TAG names a reading; 𒋳 names the written sign. A bare sign does not tell you which value the tablet uses.

Why does one sign have so many readings?

It worked as a writing sign, not a picture with one caption.

The earliest TAG cuneiform attestation appears on an Uruk III (about 3200–3000 BCE) lexical tablet—a tablet listing words. Cuneiform developed alongside urban administration: early signs recorded quantities and goods, then scribes expanded the system to write words and syllables. The sign evolved within a changing script; it was not a one-off invention. As scribes used cuneiform for Sumerian, Akkadian, and other languages, one shape could stand for several words or readings.

A TAG×TUG₂ construction shows why combined signs can have a distinct value: this compound writes the name Uttu. It is a scribal combination, not a visual resemblance; a nearby or similar sign is not automatically related.

Why does the same glyph look different in different fonts?

A font can change style; the encoded sign stays the same.

Different cuneiform fonts can target historical writing styles. The Unicode Standard 16.0 says its reference glyphs mainly follow Ur III forms, while a font may show earlier or later styles. Wedges may therefore shift in arrangement without indicating a different sign.

Enmerkar uses a transliteration-based input method: enter a reading, choose from the cuneiform candidates, then confirm with Space or Enter. The Enmerkar README describes this candidate-and-confirm flow.