Dukus Horant
Middle High German epic poem
Dukus Horant is a 14th-century narrative poem in Judeo-German (Proto-Yiddish).
Importance
Dukus Horant is the best known of a number of works which survive in the Cambridge Codex T.-S.10.K.22. This manuscript was discovered in the Cairo Geniza in 1896, and contains a collection of narrative poems in a variant of Middle High German, written in Hebrew characters. There is some controversy over the extent to which the manuscript's language differs from the commonly spoken German of the time, but it is agreed there is a strong Jewish colouring to it. Therefore, these are the oldest known works (apart from a few short inscriptions dated to the 13th century) in the Ashkenazi Jewish vernacular which later developed into Yiddish.
Dukus Horant is a heroic epic with thematic similarities to the German poem Kudrun. It is thus a good example of the transfer of literary material between the Christian and Jewish communities in the German-speaking lands in the later Middle Ages; by contrast, the other works in the manuscript contain traditional Jewish material.
Plot
The poem tells how Duke Horant is sent by King Etene to Greece, probably to Constantinople, to win the hand of the princess Hilde. However Hilde's father, the fierce Greek king Hagen, is not willing to give his daughter to Etene until Horant has proved his prowess in a series of adventures.
Form
Dukus Horant is composed in four-line rhymed strophes, the first and second line of each strophe being distichal.
This brief starts where responsible research should: with the source description of “Dukus Horant” as middle High German epic poem. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the arts & letters register because the source frames it as middle High German epic poem. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Object files, edition statements, performance records and contemporary criticism preserve different stages of the work’s history. The source revision retrieved here is dated Jun 27, 2026. The linked authority identifier is Q251848. VIAF identifies the subject as 180264832. 2 of 4 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1896.
Later fame can flatten the distinction between original context, subsequent adaptation and institutional collecting history. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Separate the work, its editions or performances, and its later reception. Catalogue records, publication histories and object files often preserve different parts of that story.
- Identifying works and editions
- Tracing reception history
- Finding collection records
The original object or edition, catalogue raisonné, performance record, rights file and holding institution.
Three-step research path
- Establish the record: confirm the title “Dukus Horant”, its source revision and the description used here.
- Expand the search: follow Dukus Horant primary sources, Dukus Horant archive and Dukus research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Dukus Horant”?
- Where is authorship, date or provenance documented?
- Which edition, object, performance or recording is being described?
Search terms from this dossier
This entry incorporates text from “Dukus Horant” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.