ROMANCE languages alias in OPUS-MT about easynmt HOT 5 OPEN

Thanks for quick response. I need to use the format f'>>pt_BR<< {text}' for both models.

from easynmt.

Hi @jubs12
Thanks for pointing this out to me. As there are so many opus-mt models, I was not able to check them all :)

The ROMANCE model supports several languages:
fr,fr_BE,fr_CA,fr_FR,wa,frp,oc,ca,rm,lld,fur,lij,lmo,es,es_AR,es_CL,es_CO,es_CR,es_DO,es_EC,es_ES,es_GT,es_HN,es_MX,es_NI,es_PA,es_PE,es_PR,es_SV,es_UY,es_VE,pt,pt_br,pt_BR,pt_PT,gl,lad,an,mwl,it,it_IT,co,nap,scn,vec,sc,ro,la

Do you know if you have to somehow specific which language your source language is? Or does it work for any of these languages without providing encoding the source language.

For the model en-ROMANCE, you have to provide as token the target language. So there I have to figure it out what a good way would be to include these multi-lingual opus-mt models.

from easynmt.

great, that is helpful.

from easynmt.

@nreimers any update on supporting these ROMANCE languages in EasyNMT? Alternatively, is there any guide on how to deploy this Opus MT Romance model in a standalone fashion? We have a need for Brazilian Portuguese translation which seems to be supported by this model. Thanks!

from easynmt.

@nreimers any update on supporting these ROMANCE languages in EasyNMT? Alternatively, is there any guide on how to deploy this Opus MT Romance model in a standalone fashion? We have a need for Brazilian Portuguese translation which seems to be supported by this model. Thanks!

I figured out how to send the language tokens as per the instructions from https://huggingface.co/Helsinki-NLP/opus-mt-en-ROMANCE and comments from @jubs12 above.

So specifying ROMANCE as the target language code, along with this works for me since I use EasyNMT as a translation server. Sample EasyNMT GET request URL path for language code pt_br (Brazilian Portuguese):

/translate?target_lang=ROMANCE&text=%3E%3Ept_br%3C%3CMoscow&source_lang=en&beam_size=2

from easynmt.