Difference between revisions of "Roadmap"

From Apertium
Jump to navigation Jump to search
 
(26 intermediate revisions by 8 users not shown)
Line 1: Line 1:
getace
This page gives a roadmap of features which we hope will be available in future Apertium releases.
This page gives a roadmap of features which we hope will be available in future Apertium releases.

== Apertium 3.0 ==

* Unicode
* Migration of <code>apertium-tagger-training-tools</code> to unicode
* Separate symbols file


== Apertium 4.0 ==
== Apertium 4.0 ==


* Transfer
** Multi-stage [[chunk]] transfer
*** aren't we already doing this?
** [[Ideas_for_Google_Summer_of_Code/Weighted_transfer_rules|Weighted transfer rules]]
** Parser (e.g. [[Ideas for Google Summer of Code/Robust recursive transfer]])
* <code>apertium-transfer-training-tools</code> and <code>apertium-tagger-training-tools</code> to multi-stage transfer.
* Discontiguous multiwords
* Multiwords with inflection on both parts, circumfix inflection (like Georgian verbs) without overanalysing
* ?
* ?
== Apertium 3.8 ==
* [[Ideas_for_Google_Summer_of_Code/Automatic_blank_handling|Automatic blank handling]]

== Apertium 3.5 ==

* ☐ TMX support
** We have some TMX support, but stuff like [[User:Pankajksharma/Patcher]] would be nicer
* ☐ [[Automatic text normalisation|Orthographic normalisation]]
* ☑] Noun-compound resolvation
** We already do [[Compounds|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
* ☑ Port to Mac OS/X
** See [[Installation]], done long time ago
* ☑ Port to Windows
** See [[Simpleton]]




[[Category:Development]]
[[Category:Documentation in English]]

Latest revision as of 10:44, 23 September 2016

This page gives a roadmap of features which we hope will be available in future Apertium releases.

Apertium 4.0[edit]

Apertium 3.8[edit]

Apertium 3.5[edit]

  • ☐ TMX support
  • Orthographic normalisation
  • ☑] Noun-compound resolvation
    • We already do compound analysis, though where longest-match doesn't give the right answer, we have to lexicalise
  • ☐ Migration of apertium-transfer-training-tools to unicode
  • ☑ Port to Mac OS/X
  • ☑ Port to Windows