dotnet / dotnet/ResXResourceManager

DeepL: unsupported languages

Open
#473 2 comments 2 reactions 0 assignees View on GitHub
Feature request Up for grabs
Dominant language
C#
Stars
1.5k
Forks
251
Avg merge
1d 1h
Merged PRs (30d)
1

Description

**Describe the bug**
A misleading error message (400: Bad Request) is returned when unsupported languages are used with the DeepL API. Since DeepL only supports a rather small subset of languages, it would be nice to be informed when a selected target language was unsupported by the API.

There is an endpoint to fetch supported langs documented here: https://www.deepl.com/docs-api/other-functions/listing-supported-languages/

**To Reproduce**
Attempt to translate text from any language to an unsupported one (e.g. Korean [ko]). The error message displayed is: `DeepL: Response status code does not indicate success: 400 (Bad Request)`

**Expected behavior**
A more helpful message should be shown (e.g. `The target language is not supported by this API`)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.