Difference between revisions of "Apertium Turkic/TODO"

From Apertium
Jump to navigation Jump to search
Line 16: Line 16:
 
* [http://www.google-melange.com/gci/task/view/google/gci2013/5891237794021376 spell checking mode in apertium-apy]
 
* [http://www.google-melange.com/gci/task/view/google/gci2013/5891237794021376 spell checking mode in apertium-apy]
 
* [http://www.google-melange.com/gci/task/view/google/gci2013/5434520367005696 integrate spell checker interface into html-tools]
 
* [http://www.google-melange.com/gci/task/view/google/gci2013/5434520367005696 integrate spell checker interface into html-tools]
* [http://www.google-melange.com/gci/task/view/google/gci2013/5157832131346432 get language detection interface working] (in progress)
+
* <s>[http://www.google-melange.com/gci/task/view/google/gci2013/5157832131346432 get language detection interface working]</s>
 
* [http://www.google-melange.com/gci/task/view/google/gci2013/5720782084767744 language detection mode in apertium-apy] (prototype done)
 
* [http://www.google-melange.com/gci/task/view/google/gci2013/5720782084767744 language detection mode in apertium-apy] (prototype done)
   

Revision as of 21:50, 12 January 2014

This is a general to-do list for the Apertium Turkic working group.

Website

This section outlines what's left to get http://turkic.apertium.com/ up and running.

software infrastructure

optional: spell checker and language detection stuff

what to include

make the following pairs available to the site:

  • pairs: kaz-tat, tur-kir, kaz-kir, tat-bak, kaz-kaa, tuk-tur?, tur-uzb?, kaz-eng?
  • transducers: kaz, tat, kir, tur, bak, chv, kum, nog, kaa, uzb?, tuk?

prettifying

future

  • consider including the web concordancer on the site (and consider what corpora to provide search access to...)

Things that need to be figured out

Issues introduced by new build process

  • How can we do single-category testvoc now?
  • How can we make vanilla transducers (without MT-specific "wrong" POSes)
    • The problem is that "! Use/xxx-yyy" lines can't just be grepped out in the vanilla transducer anymore, since those are needed for the xxx-yyy transducers. That is, we're no longer just copying the lexc file, but copying the full transducer (no trimming before compilation), and trimming the transducer directly (based on the bidix) for use in pairs.
  • How can we count trimmed stems?