• Hello,

    first of all, thanks for creating such great plugin.

    I have encountered an issue, whilst translating strings that have variables like !!this!!, enclosed in double exclamation marks. When sending these strings to DeepL or Google Translate or Yandex, these variables get translated too, which is not desired at all (it then stops working in the particular plugin that I’m translating).

    So this is potentially a feature recommendation – either to implement some basic syntaxes for variables in Loco Translate to make it aware of this, or (maybe better) allow the user to define how are variables in the currently translated plugin enclosed, and somehow communicate this to the DeepL or Google Translate (Ai had recommended me to exchange the !! for <x> and </x> pair tags, which DeepL/Gtranslate recognises as HTML and doesn’t translate them. That worked.

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

    (@timwhitlock)

    The main Loco platform already implements placeholder protection, but the feature is not yet rolled into this plugin. However – once it is – it would still only search for known syntax (like PHP printf) and would not recognise !!variable!! as a placeholder. What syntax is that?

    Thread Starter petrchutny

    (@petrchutny)

    Thanks @timwhitlock . It’s “Paid memberships pro” plugin’s strings for sending emails etc…

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.