Difference between revisions of "Apertium Turkic/TODO"
Jump to navigation
Jump to search
Firespeaker (talk | contribs) (Created page with " == Website == Get [http://turkic.apertium.com/ http://turkic.apertium.com/] up and running. === software infrastructure === * <s>Get apertium-apy working stably</s> * [http:...") |
Firespeaker (talk | contribs) |
||
| Line 23: | Line 23: | ||
== Things that need to be figured out == |
== Things that need to be figured out == |
||
* [http://www.google-melange.com/gci/task/view/google/gci2013/5872152972623872 How can we count lexc stems effectively?] - JNW's bash script can be generalised (and rewritten in python), and it'll come close |
|||
=== 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) |
|||
* How can we count trimmed stems? |
|||
Revision as of 09:02, 3 January 2014
Contents
Website
Get http://turkic.apertium.com/ up and running.
software infrastructure
Get apertium-apy working stably- merge simple-html and html-tools so that simple-html can be automatically extracted from html-tools
- apache forwarding for html-tools
- init scripts and cron testers for html-tools, gateway, and apertium-apy
optional: spell checker stuff
what to include
make the following pairs available to the site:
- pairs: kaz-tat, tur-kir,
- transducers: kaz, tat, kir, tur, bak, chv, kum, nog, kaa, uzb?, tuk?
prettifying
- localised language names in analysis and generation
- add a note (localised to various languages) along the lines of "Found a mistake? Help us fix it!" with link to Apertium Turkic
Things that need to be figured out
- How can we count lexc stems effectively? - JNW's bash script can be generalised (and rewritten in python), and it'll come close
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)
- How can we count trimmed stems?
