Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-2799

DeepL API - some languages missing compared to https://www.deepl.com/translator

XMLWordPrintable

    • Critical
    • All EN and PT DeepL language resources must be changed to EN-GB and PT-PT
    • All DeepL resources where the target language is EN or PT, will be changed from EN -> EN-GB and PT to PT-PT. The reason for this is a recent DeepL api change.

       

      The deepl api got more complex.

      Previously all available languages were available as source and target languages.

      Now some languages are only available as target languages.

      Therefore we have to adapt the integration to make all possible language combinations available in translate5.

          [TRANSLATE-2799] DeepL API - some languages missing compared to https://www.deepl.com/translator

          Thomas Lauria added a comment - - edited

          Reopened due the following problem in InstantTranslate:

          when using Instanttranslate with configured deepl resources source en target de and source de and target en-GB a language swap is not setting the correct source language since en-gb could not be found in the source dropdown.

          This must be extended so that we use a fuzzy matching to find at least one matching language in the other field on swapping languages.

          → This is solved locally on my machine, but not yet commited.

          Also it seems that it is nothing defined if the language could not be found at all.

          → This is still open, here is just used one language out of the list instead of saying not possible, or similar.

          Thomas Lauria added a comment - - edited Reopened due the following problem in InstantTranslate: when using Instanttranslate with configured deepl resources source en target de and source de and target en-GB a language swap is not setting the correct source language since en-gb could not be found in the source dropdown. This must be extended so that we use a fuzzy matching to find at least one matching language in the other field on swapping languages. → This is solved locally on my machine, but not yet commited. Also it seems that it is nothing defined if the language could not be found at all. → This is still open, here is just used one language out of the list instead of saying not possible, or similar.

            aleksandar Aleksandar Mitrev
            marcmittag Marc Mittag [Administrator]
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: