Difference between revisions of "Roadmap"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
* TMX support |
* TMX support |
||
** We have some TMX support, but stuff like [[User:Pankajksharma/Patcher]] would be nicer |
|||
* Orthographic normalisation |
* Orthographic normalisation |
||
* Noun-compound resolvation |
* Noun-compound resolvation |
||
** We do compound analysis (though where longest-match doesn't give the right answer, we have to lexicalise) |
|||
* Migration of <code>apertium-transfer-training-tools</code> to unicode |
* Migration of <code>apertium-transfer-training-tools</code> to unicode |
||
* Port to Mac OS/X |
* Port to Mac OS/X |
||
** Isn't this done long time ago? |
|||
* Port to Windows |
* Port to Windows |
||
** People have done this as well, though no one uses Windows so who knows if it still works. |
|||
== Apertium 3.0 == |
== Apertium 3.0 == |
||
Revision as of 18:43, 15 February 2015
This page gives a roadmap of features which we hope will be available in future Apertium releases.
Apertium 4.0
- Transfer
- Multi-stage chunk transfer
- aren't we already doing this?
- Parser (e.g. Ideas for Google Summer of Code/Robust recursive transfer)
- Multi-stage chunk transfer
apertium-transfer-training-toolsandapertium-tagger-training-toolsto multi-stage transfer.- ?
Apertium 3.5
- TMX support
- We have some TMX support, but stuff like User:Pankajksharma/Patcher would be nicer
- Orthographic normalisation
- Noun-compound resolvation
- We do compound analysis (though where longest-match doesn't give the right answer, we have to lexicalise)
- Migration of
apertium-transfer-training-toolsto unicode - Port to Mac OS/X
- Isn't this done long time ago?
- Port to Windows
- People have done this as well, though no one uses Windows so who knows if it still works.
Apertium 3.0
- Unicode
- Migration of
apertium-tagger-training-toolsto unicode
