Use the two-direction text form to examine possible wording, then check signs, transliteration conventions, grammar, period, and genre with specialist sources.
The provider result will appear here...
These retained pairs demonstrate the Latin-character transliteration format shown in the page content. They are starting points for comparison, not readings tied to a cited tablet, period, or published sign list.
English
Water
Translation
a
The transliteration a beside the gloss water
English
Deity / sky
Translation
dingir / an
Two readings associated with the deity or sky sign
English
Lord
Translation
en
The transliteration en beside the gloss lord
English
King
Translation
lugal
The transliteration lugal beside the gloss king
English
Person
Translation
lú
The transliteration lu beside the gloss person
English
Place / earth
Translation
ki
The transliteration ki beside the gloss place or earth
| Cuneiform | Transliteration | Gloss |
|---|---|---|
| 𒀀 | a | water |
| 𒀭 | dingir / an | deity / sky |
| 𒂗 | en | lord |
| 𒈗 | lugal | king |
| 𒇷 | lu | person |
| 𒆠 | ki | place / earth |
These common sign values show why a transliteration and a meaning are separate layers. Readings depend on their position and surrounding text.
Record what the provider response lacks before treating any line as a source-based interpretation.
| Evidence | Question | Where to Verify |
|---|---|---|
| Signs | Which signs are actually present? | Edition or tablet image with line reference |
| Transliteration | Which readings and determinatives were chosen? | Published transliteration and sign list |
| Language | What period and genre fit the grammar? | Grammar and corpus for that setting |
| Translation | Which alternatives or damaged sections remain? | Commentary and specialist review |
The forward instruction asks the provider for Sumerian cuneiform transliteration. There is no Unicode-versus-transliteration selector, so the page cannot promise a particular character representation or sign encoding.

The request contains your text and a general instruction. It does not look up a tablet catalogue number, line reference, excavation record, or a named publication before composing the answer.

Registered users receive five daily translations. After those are used, a completed request consumes one paid credit; a failed provider request is eligible for the route's credit-refund path.

For coursework, publication, museum labels, inscriptions, or quoted literature, compare the draft with a relevant edition and have a qualified reader inspect the result.

These are the implemented boundaries of the universal text interface.
The swap control selects a forward transliteration instruction or a reverse modern-English instruction and can exchange existing panel text.
The visible counter and client validation limit each page submission to 500 characters.
The page is not processed locally. /api/gemini meters the request and the compatibility queue sends it to DeepSeek.
The result is not an academic translation and does not carry a tablet citation, editorial apparatus, or specialist sign analysis.
Details about access, notation, direction, and evidence.
Check out these related translation and AI tools to enhance your experience
Keep the request short, choose the intended direction, and plan a separate evidence check.
The browser form accepts text only and blocks input above 500 characters. Include enough wording to show relationships, but avoid combining unrelated sentences.
The direction control changes the provider instruction between English-to-Sumerian transliteration and Sumerian-transliteration-to-English. A signed-in account is required by the shared route.
Check the response against a cited sign list, lexicon, grammar, and edition that match the source. Ask a Sumerian specialist or Assyriologist to review important use.
Choose a direction, submit up to 500 characters, and compare the returned draft with source-specific references.