Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.


From Apertium
Jump to: navigation, search


Uzbek - o'zbek tili, ўзбек тили
language transducer
Coverage: ~82.9%
Stems: 4094
Vanilla stems: 4094
Paradigms: 1
Families: Turkic languages
Areas: Languages of Central Asia, Languages of the former Soviet Union
Lang info Uzbek

Apertium-uzb is a morphological analyser/generator and CG tagger for Uzbek, currently under development. It is intended to be compatible with transducers for other Turkic languages so that they can be translated between. It's used in the following language pairs:

A recent version of the transducer is running live at turkic.apertium.org and can be tested in its analysis and generation capabilities there.

[edit] Current State

  • Number of stems: 4094
  • Disambiguation rules: 48
  • Coverage: ~82.9%

wikipedia 1.2M ~82.9%

[edit] Installation

Apertium-uzb is currently located in languages/apertium-uzb.

[edit] Developers

[edit] oʻ and gʻ

The Uzbek letters ‹oʻ› and ‹gʻ› are properly written using ‹ʻ›, unicode character 02BB, "modifier letter turned comma". Use of other apostrophe letters is incorrect.

[edit] Dealing with Cyrillic and Latin

[edit] Plan A

There will be two separate lexcs and twols (.lat and .cyr) with the continuation lexica and rules and all, though you may be able to get by with one twol considering how simple things are. There will also be a master .dix, in Latin, with comments in a standarised format in Cyrillic (also possible the other way around).

There will also be a simple script to check for dix entries without Cyrillic comments in the standard format in the master .dix, and automatically generate them, updating the Cyrillic dix, outputting "TOCHECK" or something in a comment with the converted words. Someone then goes through and checks anything with "TOCHECK", and fixes / gets rid of "TOCHECK".

This is how we can trivially "convert" the dix to Cyrillic, and even convert the stems in lexc when we copy/update it from -uzb.

[edit] Plan B

The Cyrillic lexc and dix will be generated from the Latin-script ones.

A script will take all the stems from dix and automatically convert them to Cyrillic, updating a three-column text-file database (Latin Cyrillic Checked). The Checked column will have two states: TOCHECK, GOOD. This will allow a checker to fix the output of the conversion script for corner cases (mostly Russian words). This script (although slow) covers the edge cases and produces good results.

Another script will then generate a Cyrillic version of dix and lexc from the Latin-script versions, using the above mentioned database.

[edit] Final Plan

We'll go with Plan B, with file names roughly like this:


To do:

  • Hand-convert the morphotactics (in lexc) and morphophonology (twol) to Cyrillic..
  • Future development of either morphotactics (in lexc) or morphophonology (twol) must be done in parallel (i.e., both Latin and Cyrillic versions will need to be updated with any changes)!
  • Write a short script that dumps all [new] stems from the lexc file and uses the transliterator script to update any entries not marked as GOOD.
  • Write a short script (that uses the lexc parsing script Sushain developed as a library?) that replaces stems in certain categories (e.g., not numbers and other truly closed categories) in the uzb_Cyrl.lexc file based on the uzb.lexc and Latn-Cyrl.tsv files.
  • Update modes file to support Cyrl stuff.
  • Write disambiguation rules to be as script-agnostic as possible. For word-specific rules, make a version for each script?
  • Develop a plan for pairs, e.g.:
    • In uzb-kir, add _Cyrl.dix, _Cyrl.lrx (could also be automatically generated), and even transfer files (???)...
    • Set up conversion of stems using same tsv file and similar scripts..
    • Update modes file for _Cyrl
Personal tools