@cheeaun @box464 Yeah, DeepL work a lot better for Korean or Japanese at least! It would be great if it falls back to Lingva if a language is not supported by DeepL. 🤔

@hongminhee @box464 oh interesting 🤔 I have the fallback idea too, so in the end, it's not just one but multiple translation providers to handle wider range of languages.

A single API/library wrapper for multiple translation providers would be cool (I haven't look into this) but yeah, this requires some extra work + UI to configure.

I picked Lingva because I needed bigger list of language support and for my needs, transliteration text, which only Lingva (Google Translate) provides 😬