• Hello there

    We’re trying to translate with deepl.
    So we do what everyone does, register account, save apikey and url, translate.

    Problem is: in your file /pub/js/min/admin.js you have a fixed reference for deepl called:
    source_lang: “EN”

    So basically our (german) texts can’t be translated. Because the main language of our installations are in german this is a problem. Can you make this language configurable?
    I tried it by changing the var to “DE” directly in your file and then translations are showing up as expected.

    FYI:
    In another topic you stated that the green “EN” note is not relevant for loco, but it seems now with deepl it is ??

    Thank you ??
    Christian

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tim W

    (@timwhitlock)

    You are right that Loco Translate does not care what language your sources are actually written in, but making this configurable in the near future is not a priority, because rightly or wrongly it goes against WordPress convention to have a non-English source locale.

    Related: https://localise.biz/wordpress/plugin/faqs/non-english-source

    You will have to modify admin.js if you want to get around this for the time being.

    Thread Starter pxmkosh

    (@pxmkosh)

    Hi Tim

    Thank you for the fast reply.
    I can understand your argument but I really don’t get it why it’s not way to have a setting because there is a world outside english speaking countries and if you built websites in french or german it makes totally no sense to has english as base-language and translate every string every time ??

    But thanks, have a nice one ??
    Christian

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘deepl translation failing with other base-language than EN’ is closed to new replies.