Some translated strings aren’t reflected in emails

  • Resolved Yuval

    (@yuvimo)


    4 years, 5 months ago

    Hello,

    It looks like there are some inconsistencies with string translations. Namely the source of the translations.

    Some strings reflect Kadence’s PO/MO files, some strings seem to only reflect WooCommerce’s PO/MO files, and some string simply don’t translate, no matter if the strings I use exists (and are translated) in either Kadence or WooCommerce’s PO/MO files.

    This happens in the email ‘Body Text’ field of the “Customer Processing Order” email for example. It’s as if the field doesn’t see the any of the translation files.
    It happens in other email fields as well.

    Extremely frustrating.
    Many thanks,
    Yuval

Viewing 9 replies - 1 through 9 (of 9 total)
  • hannah

    (@hannahritner)

    4 years, 5 months ago

    Hi Yuval,
    Thanks for reaching out. Sorry for your frustrations. I’ll pass this along to the developer and get some feedback from him as soon as he’s available.
    Thanks for your patience!

    Kindly,
    Hannah

    Thread Starter Yuval

    (@yuvimo)

    4 years, 4 months ago

    Thanks a lot Hannah!

    In case it helps, here are the fields where the text isn’t being translated, even though the strings are in Kadence WooCommerce Email Designer’s language files.
    – Customer processing order
    – Customer new account
    – Customer password reset
    All in the ‘body’ field.

    Thank you for trying to solve this!

    Plugin Contributor Ben Ritner – Kadence WP

    (@britner)

    4 years, 4 months ago

    Hi,
    The body field is an input field. You can place any text in any language you want into it. It’s not a static string that you translate it’s a place to add content.

    Does that make sense?

    Ben

    Thread Starter Yuval

    (@yuvimo)

    4 years, 4 months ago

    Hi Ben,

    Thank you for your reply.
    This would make sense if there was no need to have emails going out in multiple languages, and also if the body text did not already contain crucial text by default.

    Even Kadence’s POT file contains strings that are clearly meant to go in these fields.

    These strings really are crucial, so it looks like at the moment Kadence can’t be properly used in multilingual sites.

    Thanks,
    Yuval

    hannah

    (@hannahritner)

    4 years, 4 months ago

    Hi Yuval,
    Are you running a multilingual plugin? If so, which one? You should be able to translate each of these fields when editing in each language, as you would for content on your site. Let me know if this is not the case for you!

    Kindly,
    Hannah

    Thread Starter Yuval

    (@yuvimo)

    4 years, 4 months ago

    Hi Hannah,

    Thank you for the follow up.
    The site is currently not multilingual.

    It’s planned to be multilingual in the future, and I’ll be using TranslatePress to achieve that. I believe that due to the way TranslatePress works, it doesn’t have the option to translate the emails – TranslatePress doesn’t detect the strings in the email templates (as far as I know).

    Translation for emails works out-of-the-box in WooCommerce, so it’s a shame Kadence can’t be consistent with that.

    For now, I have just set the text to be in the one language currently being used.
    I will have to figure out something else later on, when moving to a multilingual setup. Most likely style WooCommerce’s email templates directly instead of using a plugin.

    Thanks for your help,
    Yuval

    hannah

    (@hannahritner)

    4 years, 4 months ago

    Hi Yuval,
    With TranslatePress you would just need to use their conditional shortcodes. This thread may be helpful for you: https://ww.wp.xz.cn/support/topic/translation-of-custom-text-e-g-body-text/

    Kindly,
    Hannah

    Thread Starter Yuval

    (@yuvimo)

    4 years, 4 months ago

    Thanks a lot Hannah, I’ll give it a try.

    hannah

    (@hannahritner)

    4 years, 4 months ago

    No problem! Let us know if we can assist you further.

    Best,
    Hannah

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

The topic ‘Some translated strings aren’t reflected in emails’ is closed to new replies.