ROMANCE languages alias in OPUS-MT
See original GitHub issueHello, congrats for the initiative!
I’ve been using Helsinking-NLP models previously and most commonly used models are ‘opus-mt-en-ROMANCE’ and ‘opus-mt-ROMANCE-en’ for Portuguese. So, if I use model.translate(sample, source_lang='pt', target_lang='en')
, it won’t work, but as I’ve tested, model.translate(sample, source_lang='ROMANCE', target_lang='en')
works.
So, It would be nice to have some alias in the code for ROMANCE. 😃
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Helsinki-NLP/opus-mt-en-ROMANCE - Hugging Face
We're on a journey to advance and democratize artificial intelligence through open source and open science.
Read more >One Question Answering Model for Many ... - DeepAI
07/26/21 - We present CORA, a Cross-lingual Open-Retrieval Answer Generation model that can answer questions across many languages even when ...
Read more >arXiv:2107.11976v2 [cs.CL] 28 Oct 2021
target language without any translation or in-language retrieval modules as ... Dowmunt et al., 2018) and trained on the OPUS-MT dataset ...
Read more >One Question Answering Model for Many ... - OpenReview
The translation models are obtained from MarianMT (Junczys-. Dowmunt et al., 2018) and trained on the OPUS-MT dataset (Tiedemann, 2012). Monolingual baseline ( ......
Read more >Appendix A Details of Modeling - NIPS papers
same language family branch (e.g., Thai), or (iii) a language uses Latin script ... Some of the newer OPUS-MT models require a prefix...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for quick response. I need to use the format f’>>pt_BR<< {text}’ for both models.
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 codept_br
(Brazilian Portuguese):