Difference between revisions of "User:Firespeaker/Wishlist"
Jump to navigation
Jump to search
Firespeaker (talk | contribs) |
Firespeaker (talk | contribs) |
||
Line 14: | Line 14: | ||
*** allow running of multiple instances on different ports |
*** allow running of multiple instances on different ports |
||
** set up client to cycle through a list of servers and ports if the default is not responding |
** set up client to cycle through a list of servers and ports if the default is not responding |
||
** or would it be better to have a central gateway that |
*** or would it be better to have a central gateway that does this? |
||
* get bible aligner working (or rewrite it) |
* get bible aligner working (or rewrite it) |
||
Revision as of 21:54, 8 October 2013
The following are projects that I would love to see working as part of apertium.
Contents
Current smallish things
Maybe for GCI 2013?
- libvoikko support for MS Word (might not be possible)
- online spell-check interface using apertium API
- interface
- code to check via API
- get apertium-apy working correctly for Turkic pairs
- features for apertium-apy
- better error handling for apertium-apy
- write init script for apertium-apy
- with crash-detection?
- allow running of multiple instances on different ports
- set up client to cycle through a list of servers and ports if the default is not responding
- or would it be better to have a central gateway that does this?
- get bible aligner working (or rewrite it)
integration of twol debugger into apertium-quality
- I'd also reallly like to see someone adopt apertium-quality and maintain it
module for templatic syntax
- also, for e.g. compound verbs some sort of interlanguage
- integrated into bidix format?
- also, for e.g. compound verbs some sort of interlanguage
an extra module to convert numbers and alphabetisms and acronyms to words (based on something in lexc) so that phonology can happen and then back to its original form
- you'd need some notation like 10:%{он%} so the form is extracted and popped back in
- this is likely to only work on stems that don't change, at least with a non-complicated implementation (but that's fine for most Turkic languages)
Bugs
HFST :0 context bug
-
%{A%}:ә <=> [ :FrontVow :Cns* :Cns ]/[ %>: | % | :0 ] _ ;
except
[ %{ъ%}: ]/[ %>: ] _ ; %{A%}:ә <=> [ :FrontVow :Cns* :Cns ]/[ %>: | % | [ :0 - %{ъ%}: ] ] _ ;
- (2) avoids applying after %{ъ%}:0 %>:0 and (1) does not, but these should really work the same way