We already started testing Apertium Translation API on our real forum. We set logs, so after some time we will be able to tell more about real performance.
At this moment vBET supports 30 language pairs from Apertium (there is more but not common for other translation engines). We already see that adding Apertium to vBET is good idea even if performance is not the best (after all we have cache so net time it is immediate). We see it in logs - where other limits was reached now we are still able to do translations thanks to Apertium. At this moment from logs we see that mostly those are translations from English (most content here is in English) to: es, ca, gl Of course it is supported more.
To see full list of supported language pairs please see here: http://api.apertium.org/json/listPairs
Those are language pairs which now will NOT be supported (at least now):
Code:
oc => es
es => ca_valencia
oc_aran => ca
an => es
fr => eo
nb => nn_a
ca => en_US
ca => oc_aran
nn => nb
ca => oc
oc_aran => es
es => eo
oc => ca
br => fr
en => eo
ca => eo
es => oc_aran
nn => nn_a
es => pt_BR
es => oc
es => an
eo => en
nn_a => nn
es => en_US
nb => nn
We will not support it now, because there is no all-to-all support and other engines do not have such languages. We will still check does some codes cannot be just mapped in case if same language with other codes is used in other translation APIs. Anyway in first release supporting Apertium we will not support all pairs.
We want (and are ready to do it now) to use Apertium for those language pairs:
Code:
bg => mk
ca => en
ca => es
ca => fr
ca => pt
cy => en
da => sv
en => ca
en => es
en => gl
es => ca
es => en
es => gl
es => pt
es => ro
eu => es
fr => cs
fr => es
gl => en
gl => es
gl => pt
is => en
it => ca
mk => bg
mk => en
pt => ca
pt => es
pt => gl
ro => es
sv => da
Should be 30 of those. If we miss something please let us know. Also if you will get information about new language pairs supported, then also please let us know.