Some texts are not translated.

  • I have Loco Translate plugin version 2.7.1 in my store, and with its help I wanted to translate some shipping texts in emails to the customer.

    In the Loco Translate plugin menu, I found the plugin whose texts I want to translate. I found the right language and assigned the translations. It seems that everything is OK.

    Unfortunately, the customer receives emails with untranslated texts.

    I checked in the code of the plugin whose texts I want to translate. It seems that the strings are prepared correctly for translation:

    _e( ‘Track shipment: ‘, ‘woocommerce-dhl’ );
    or
    _e( ‘Shipment’, ‘woocommerce-dhl’ );

    I would like the above to be displayed in German.

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

    (@timwhitlock)

    I can’t help with issues sending WooCommerce emails. What plugin does that text domain belong to?

    What happens if you disable Loco Translate, and store your translations in the default WordPress languages directory?

    Are you sure these texts aren’t also held in the database as site settings? Often plugins allow texts like this to be customized via admin screens. This breaks file-based translation.

    Thread Starter siutek

    (@siutek)

    This text domain belongs to the DHL WooCommerce plugin, by Octolize. It is strange that some texts are translated correctly, and with some there is a problem. I have not tried disabling loco translate and copying the language file to the default location.

    Plugin Author Tim W

    (@timwhitlock)

    This text domain belongs to the DHL WooCommerce plugin, by Octolize.

    This is a commercial plugin. This severely limits the help I can give you.

    It is strange that some texts are translated correctly, and with some there is a problem

    It’s pretty common. It’s possibly a good sign, because if the texts are from the same file as the missing ones, then you know the file is being loaded (hence file loading would not be the problem).

    ?I have not tried disabling loco translate and copying the language file to the default location.

    Please do this. It’s the first step to diagnosing your fault. As your plugin is commercial, it should be safe to use the “system” location, which means Loco Translate is not actually required for loading it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.