ArticleslgStudy

science

Trojan script

Trojan script is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Trojan script rather than just read about it. In short: The Trojan script is a series of signs of unknown origin found on vessels from Troy excavated by Heinrich Schliemann's expedition. Their status is disputed and it is unclear whether they constitute a single system of writing, or if they are writing at all.

Trojan script — main illustration
Trojan script — illustration

Key takeaways

  • Trojan script belongs to science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Trojan script to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Trojan script from memory before moving on to harder problems.

Reference excerpt

The Trojan script is a series of signs of unknown origin found on vessels from Troy excavated by Heinrich Schliemann's expedition. Their status is disputed and it is unclear whether they constitute a single system of writing, or if they are writing at all. Nevertheless, several mutually-exclusive readings of these inscriptions have been proposed over the years.

Analysis

While excavating the archeological phase of Troy now known as Troy II, Heinrich Schliemann unearthed various objects he believed to depict a Trojan script. These include: a vase found within the royal palace, two terracotta seals, a red slate, and two clay spindle whorls. He was especially interested in the text on the vase, which, by his account, contained a letter similar to the modern "P." Schliemann initially attempted to translate the inscriptions based on the Cypriot syllabary. Émile-Louis Burnouf, a leading orientalist, racialist, and friend of Schliemann during the time, believed these inscriptions represented an ancient Graeco-Asiatic alphabet. Professor Martin Haug, another contemporary scholar, argued that the inscriptions were connected to the Phoenician alphabet and the Cypriot syllabary.

Philologists attempted to transliterate the signs as Greek. Professor Haug attempted to translate the seal; he claimed to have read the words “ta.i.o.si.i.go.” Haug believed this meant “to the divine Sigo.” He argued that the deity “Sigo” appeared in the names of Sigeum, Scamander, and Sicyon. Austrian classical philologist Theodor Gomperz attempted to decipher this same inscription. Although Gomperz utilized the same method as Haug, he instead chose to read the seal from right to left instead of from left to right. He claimed it translated to “to the divine commander." Gomperz went on to translate four more terracotta seals. However, other scholars were alarmed that perfect Greek had been found in Trojan inscriptions, and the inscriptions should predate the form of Greek which was used. These translations were soon revealed as erroneous; they had been based on a mistranslation of the Cypriot script. British Assyriologist Archibald Sayce attempted to read the translation utilizing more recent advancements in academic understanding of the Cypriot syllabary. Professor Sayce believed that the Trojan inscriptions were copies of a Babylonian script and were influenced by the Hittites. In 1994 Dr. Louis Godart republished the inscriptions and identified the script as Linear A. This identification has been controversial: archeologist Massimo Perna rejects this theory as "highly unlikely." According to Perna, the signs found on the spindle whorls appear in numerous other ancient scripts and ornaments, and that any analysis of the signs is problematic due to inability to analyze the original finds. Alternately, Edwin L. Brown argued they were written using Linear A to transcribe a dialect of the Luwian language. Luwian was a lingua franca in late Bronze Age western Anatolia, and as yet the only accepted evidence of writing at Troy is a scribal seal inscribed with Luwian hieroglyphs found in Troy VIIb1. However a single inscription on a very portable object "can hardly be used as evidence that the population of Troy spoke Luwian." Another inscription in the Trojan script was found in Troy II. Soviet historian of antiquity Nikolay Kazansky found them more similar to Linear B signs, while another Soviet historian, Arkady Molchanov, regarded them as "imitation of writing". Regardless of any similarities the Trojan symbols have with Linear B, those from Troy II date from about a thousand years before the development of that script. Archaeological analyses of the inscriptions have indicated that Troy III (2250–2100/2050 BCE) and Troy IV (2100/2050–2000/1950 BCE) predate Linear A, Troy V (2000/1950–1900/1850 BCE) coincides with linear A, and Troy II (2600/2550–2250 BCE) may be an intermediate link to Bronze Age societies such as the Usatove or Ezero cultures.

Claimed readings of inscriptions

According to Ukrainian linguist Iurii Mosenkis's theory that the Trojan script represents an early and archaic variant of Linear A, Inscription № 2444 may be read:

ku-pa a-ro-ma ku-pa a-ro-ma Inscription № 2445 is illegible and seems to have partly deteriorated; several signs may be identified as fragments of Linear A or Linear B signs but not as whole signs. Classicist Edwin L. Brown claimed that two of the spindle whorls can be read as "PI-MI-D/MI-D/TA." “PI-MI-D” can be translated as “Pimidas”, a personal name in the possessive genitive. “Pi” or “Piya” appears in many ancient Anatolian names such as Piyamarandu or Pissillis. Similarly, “MI-D/TA” appears frequently in ancient Anatolian names such as Mita, Mida, and Midas. In Luwian hieroglyphics the name “Mita” means “servant.” However, in this context it may refer to devoted servitude of a deity. “Puri(y)as” may be read as a noun in the nominative singular or plural form” It is possible that this word is a cognate with the Hittite word “Purpura,” meaning “dumpling” or “lump.” If “Puri(y)as” shares the same meaning, then the term may refer to the spindle whorl itself, which was made of a lump of clay. It is possible the entire sentence may be translated to read: “Pimidas’s spindle whorl” or perhaps as “The spindle whorl is Pimidas’s.”

See also Alphabets of Asia Minor Cypro-Minoan syllabary Old European script Trojan language Teucer Undeciphered writing systems

References

Sources

Illustrations

Trojan script: Depiction of two of the spindle whorls.[6]
Depiction of two of the spindle whorls.[6]

Worked examples

Example 1 — a first encounter with Trojan script

Start with the simplest possible case. Write down what Trojan script claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Trojan script before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Trojan script ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Trojan script

In research
Trojan script appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Trojan script in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Trojan script is common in secondary-school and first-year university syllabi. It links to neighbouring topics Ancient Greek language stubs, Heinrich Schliemann, Linear A, so understanding it makes those chapters shorter.
In everyday life
Look for Trojan script outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Trojan script” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Trojan script in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Trojan script means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Trojan script out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Trojan script in simple terms?

The Trojan script is a series of signs of unknown origin found on vessels from Troy excavated by Heinrich Schliemann's expedition. Their status is disputed and it is unclear whether they constitute a single system of writing, or if they are writing at all.

Why does Trojan script matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Trojan script?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Trojan script.

Tags

  • Ancient Greek language stubs
  • Heinrich Schliemann
  • Linear A
  • Troy
  • Writing system stubs

Keep exploring