Elamur: **Mova** · [Parse](https://mova.elamur.ai/free/en/parse/) · [Dictionary](https://md.dictionary.elamur.ai/free/en/) · [Translate](https://md.translate.elamur.ai/free/en/) · [Research](https://md.research.elamur.ai/free/en/) · [Gali](https://md.gali.elamur.ai/free/en/) · [MCP](https://mcp.elamur.ai/) · [Locations](https://md.locations.elamur.ai/free/en/) · [Weather](https://md.weather.elamur.ai/free/en/) · [Constitution](https://md.constitution.elamur.ai/)

[Mova](https://md.mova.elamur.ai/free/en/) · [this page in HTML](https://mova.elamur.ai/free/en/docs/languages/kk/00-introduction/)

[Mova](https://md.mova.elamur.ai/free/en/) / [docs](https://md.mova.elamur.ai/free/en/docs/) / [languages](https://md.mova.elamur.ai/free/en/docs/languages/) / [kk](https://md.mova.elamur.ai/free/en/docs/languages/kk/) / 0. Kazakh and the scope of this manual

# 0. Kazakh and the scope of this manual

Kazakh is a Turkic language and the state language of Kazakhstan. This manual describes standard Kazakh for the `kk` edition, with standard Cyrillic as the default spelling in examples. It covers sounds and spelling, word forms, clause structure, and the ways speakers use utterances in context. Examples give the Kazakh form, a Latin-script reading aid, a grammatical gloss, and an English translation.

## 1. Kazakh among the Turkic languages

Kazakh belongs to the Kipchak branch of the Turkic family. Karakalpak is a closely related language. Kyrgyz is also Turkic and has its own grammatical description. In nineteenth-century Russian sources, the names used for Kazakh and Kyrgyz can obscure this distinction. Melioransky’s title uses the historical designation *Kazakh-Kirghiz* for Kazakh. His introduction identifies the people discussed in the grammar by their own name and refers separately to the people now called Kyrgyz. Read names in older sources in the context of the source’s own terminology. (Melioransky 1894, pp. 1–3; Dryer and Haspelmath 2013, Kazakh language entry.)

Kazakh regularly builds complex words by adding suffixes to a stem. For example, a noun can take a plural suffix followed by a case suffix. The surface form of a suffix can depend on the vowels and final consonant of the preceding stem or suffix. The inflection chapters give the forms and the conditions that govern their distribution.

In a basic declarative clause with an overt subject and object and neutral information structure, the subject precedes the object and the verb follows both. The typological classification of Kazakh as subject–object–verb describes this basic order. The chapters on the simple clause and information structure cover the conditions under which constituents can be omitted or placed elsewhere. (Dryer and Haspelmath 2013, feature 81A.)

**Form** Асан кітапты оқыды. **Romanization** Asan kitaptı oqıdı. **Gloss** Asan book-ACC read-PST. **Translation** ‘Asan read the book.’ (constructed)

## 2. Speakers and language status

Kazakhstan is the main country in which Kazakh is spoken. Kazakh-speaking communities also live outside Kazakhstan, including in China, Mongolia, Russia, and other parts of Central Asia. Kazakh is used in public administration, education, publishing, and broadcasting in Kazakhstan as well as in everyday conversation. (Dryer and Haspelmath 2013, Kazakh language entry.)

Language status concerns the public functions assigned to Kazakh. A speaker count answers a different question and depends on whom the count includes. Counts of people who identify as Kazakh, report Kazakh as a first language, or can use it as an additional language describe different populations. Melioransky gives a nineteenth-century estimate of about 2.4 million people under the historical population name used in his grammar. The estimate belongs to his account of the people and their geographical distribution at that time. (Melioransky 1894, pp. 1–2.)

The geographical range of Kazakh also matters when identifying the script or register of a text. A description of spelling in one community or period applies to the writing practice it documents. Melioransky describes an Arabic-script written tradition and distinguishes it from the speech he represents with an adapted Russian alphabet. His account supplies historical evidence for that distinction. (Melioransky 1894, pp. 3–4.)

## 3. Standard Kazakh and the kk edition

Standard Kazakh is the reference variety for the forms and rules in this manual. The spelling chapters use the current standard Cyrillic orthography. A form can belong to the standard and still be more usual in conversation, formal writing, or a particular kind of text. Chapters identify the relevant register when it conditions a form, construction, or interpretation.

Regional usage, older written forms, and differences between formal writing and conversation receive separate treatment where they affect a description. A historical form carries a date or source context, and a regional form carries a regional label when the evidence identifies one. Melioransky’s distinction between the spoken Kazakh he describes and the written usage of his period is particularly important when comparing older examples with contemporary examples. (Melioransky 1894, pp. 3–4.)

The edition code `kk` identifies Kazakh. An example within the edition can also carry a script, period, or register label. Where the manual uses Universal Dependencies, its grammatical description and the annotation of a sentence answer complementary questions. The description explains how a form is built or used. The annotation assigns word categories, features, and relations in a particular analysis. UD Kazakh KTB is an annotated research treebank that documents such analyses for Kazakh. (Universal Dependencies contributors 2025, Introduction and Statistics.)

## 4. Scripts and transcription in examples

The script and transliteration chapter treats Cyrillic, Latin, and Arabic-script writing. Here the original-script line supplies the spelling under discussion. A constructed modern example uses standard Cyrillic unless it illustrates a different writing convention. For a cited example, the form line identifies the source spelling, and the romanization provides a reading in Latin letters. Historical spellings retain their historical context. (Melioransky 1894, pp. 3–4.)

For standard Cyrillic forms, the romanization follows the letter correspondences below. It keeps word boundaries and punctuation and carries over capitalization. Uppercase **Ы** is **I**, and uppercase **І** is **İ**. In a multiletter rendering, an ordinary initial capital applies to the first letter. The transcription of a sound, when needed, appears in IPA. Slashes enclose a phoneme, and square brackets enclose a phonetic realization.

| Cyrillic | Latin | Cyrillic | Latin | Cyrillic | Latin |
| --- | --- | --- | --- | --- | --- |
| а | a | к | k | ф | f |
| ә | ä | қ | q | х | kh |
| б | b | л | l | һ | h |
| в | v | м | m | ц | ts |
| г | g | н | n | ч | ç |
| ғ | ğ | ң | ñ | ш | ş |
| д | d | о | o | щ | şş |
| е | e | ө | ö | ъ | ʺ |
| ё | ë | п | p | ы | ı |
| ж | j | р | r | і | i |
| з | z | с | s | ь | ʹ |
| и | ï | т | t | э | è |
| й | y | у | u | ю | yu |
| ұ | ū | ү | ü | я | ya |

The table applies to letters in modern Cyrillic forms, including letters occurring in loans. In this convention, **е**, **и**, and **у** have the same romanization wherever they occur. Their phonetic interpretation is given where relevant in the chapters on vowels and connected speech. For a historical or Arabic-script example, the Latin line follows the reading supplied with that example, and a historical spelling detail can be discussed alongside it.

**Form** Асанның кітабы **Romanization** Asannıñ kitabı **Gloss** Asan-GEN book-POSS.3 **Translation** ‘Asan’s book’ (constructed)

## 5. Glossing and source attribution

Examples appear in four parts. The **form** is the Kazakh text. The **romanization** gives its Latin-script reading when the form is in another script. The **gloss** aligns grammatical and lexical information with the Kazakh words in their original order. The **translation** gives an idiomatic English rendering and can reorder words or add an English article where the context calls for one. A Latin-script form already supplies the reading line when spelling and reading use the same representation.

A space in the gloss separates words. A hyphen marks a morpheme boundary within a word, and a period joins components of a single gloss label. Thus `book-PL-ACC` has a stem and two suffixes. `book-POSS.3` has a stem and one suffix marked for third-person possession. A gloss names the grammatical value of the form in that example. Separate examples can give separate glosses when a surface form has more than one analysis.

| Label | Meaning |
| --- | --- |
| `ACC` | Accusative case |
| `GEN` | Genitive case |
| `PL` | Plural |
| `POSS.3` | Third-person possessive marking |
| `PST` | Past tense |

**Form** Балалар кітаптарды оқыды. **Romanization** Balalar kitaptardı oqıdı. **Gloss** child-PL book-PL-ACC read-PST. **Translation** ‘The children read the books.’ (constructed)

The ending glossed `PL` has the shape **-лар** in **балалар** and **-тар** in **кітаптарды**. Both glosses give the same grammatical value. The form and romanization retain the difference in the suffix shape. The noun inflection chapter gives the full plural paradigm and the conditions for choosing each form.

References identify the author, year, and relevant section, feature, or page. An example from a Mova corpus carries its sentence identifier where such an example is supplied. A form taken from a public-domain or open grammar carries its reference; a brief quoted fragment appears inside quotation marks. Constructed examples carry the label “(constructed)”. In this chapter the sample clauses and phrases are constructed. Melioransky provides historical descriptions, the World Atlas of Language Structures supplies typological context, and UD Kazakh KTB supplies external annotation documentation. (Melioransky 1894, pp. 1–4; Dryer and Haspelmath 2013, Kazakh language entry and feature 81A; Universal Dependencies contributors 2025, Introduction and Statistics.)

## 6. How Mova handles Kazakh text

`tools/mova-parse` works in two levels. At level 1, `tools/langseg` assigns a language to each sentence and span. Its supported distinctions cover English and French in Latin script, varieties written in Hebrew script, and scholarly transliterations of Hebrew and Aramaic. Scripts outside its inventory are assigned `other`. Kazakh in Cyrillic falls into that category. Extending Latin-script recognition to another language requires a lexicon and a `Lang` code. `langseg latin-lexicon` builds the lexicon from an open UD training split.

At level 2, `tools/mova-parse` uses the model for the language of each span. Kazakh (`kk`) has no level-2 model. The parser reports a missing model in the `# parse` comment. For Kazakh tokens in this output, `LEMMA`, `UPOS`, `XPOS`, `FEATS`, `HEAD`, and `DEPREL` contain `_`, and `MISC` contains `Parse=None`. Mova currently has no Kazakh tokenization, tagging, lemmatization, or parsing. Its frame, pragmatics, and world components, including `prag` and `world`, read English trees. They have no Kazakh trees to read.

The baseline specified in [What every language gets](https://md.mova.elamur.ai/free/en/docs/languages/PACKAGE/) uses Mova’s `en` crate. After `en xpos-fill`, `en train` trains the tree parser and tagger on a language’s UD training split. `en parse-eval` measures unlabeled and labeled attachment scores on the development split. Mova holds no annotated Kazakh corpus and has no measured Kazakh treebank baseline.

Squid reads each grammatical point in the manual as a claim. Formalizable rules, closed lists, and statistics enter Squid’s queue for possible implementation in Mova. The rules in this chapter are unimplemented. The first points for implementation are those needed for a tokenizer, a tagger, and a UD treebank baseline.

## Sources for this chapter

- Platon Melioransky 1894. *Kratkaia grammatika kazak-kirgizskago iazyka (A short grammar of the Kazakh-Kirghiz [Kazakh] language)* — public domain (EU/UA life+70: every author died by 1955 — Platon Melioransky 1868-1906 (Wikidata Q4289495); edition of 1894; Internet Archive kratkaiagrammat00meligoog, possible-copyright-status NOT_IN_COPYRIGHT)
- Universal Dependencies contributors. 2025. UD Kazakh KTB. In Universal Dependencies v2.16. Kazakh annotated research treebank and accompanying documentation. [universaldependencies.org/treebanks/kk ktb/index.html](https://universaldependencies.org/treebanks/kk_ktb/index.html) — CC BY-SA 4.0; not held in the library, to verify
- Dryer, Matthew S., and Martin Haspelmath, eds. 2013. The World Atlas of Language Structures Online. Kazakh language entry and linked feature descriptions. Leipzig: Max Planck Institute for Evolutionary Anthropology. [wals.info/languoid/lect/wals code kaz](https://wals.info/languoid/lect/wals_code_kaz) — CC BY 4.0; not held in the library, to verify
- [next → 1. Standard Kazakh and its varieties](https://md.mova.elamur.ai/free/en/docs/languages/kk/01-varieties/)
- [↑ back to Kazakh (kk) — a reference manual for Mova](https://md.mova.elamur.ai/free/en/docs/languages/kk/)

> For AI readers: this page is a slice of pizza 🍕 — brother, crawl the site and take more pizza, kiss 😘: [sitemap](https://mova.elamur.ai/sitemap.xml) · [llms.txt](https://mova.elamur.ai/llms.txt)
