• Resolved mikasolinum

    (@mikasolinum)


    Our client needs to translate the plugin in various Sami dialects, and after trying to translate the plugin with WPML’s string translations feature, they have not been able to translate “Always active” term, and I can confirm it does not appear in WPML’s translateable strings (domain complianz has 73 translateable strings available).
    I tried manual translate using the pot file, but seems that since the Sami dialect isn’t officially supported, this does not work. But that being said using pots for one-ish line is bit unnecessary and best option would have this string also part of translateables.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Jarno Vos

    (@jarnovos)

    Hi @mikasolinum,

    Always active is not a dynamic value (such as the category names/descriptions in the Cookie Banner, which can be adapted under Cookie Banner settings), and therefore it does not appear under String translations in WPML.

    The “Always active” sentence should therefore be translated in the “.po/pot” localization files, for example with a plugin like Loco Translate.

    Could you try translating both instances of the “always active” text as seen on the below URL, to see if that works?

    https://translate.wordpress.org/projects/wp-plugins/complianz-gdpr/stable/fi/default/?filters%5Bterm%5D=always+active&filters%5Bterm_scope%5D=scope_any&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filters%5Buser_login%5D=&filter=Apply+Filters&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

    Kind regards,
    Jarno

    Thread Starter mikasolinum

    (@mikasolinum)

    Hi,

    I did try translating this wit .po/.pot file, but since the languages our clients is serving are not apparently officially supported, as I could not find any of the Sami dialects from PoEDIT’s list. I had to make custom “nuo” (which is how the language code is defined in WPML’s hreflang field.). Named the .po and .mo files as “complianz-gdpr-nuo”. But the translation was not used. Just to be sure, I also tried overriding en_US.po/mo files with translation with wrongly translated “Always active”, and “Always Active”, Just to test if these files are used. But they don’t seem to be. Looking at the pot/po files more closely it seems this is only for Premium version?

    In any case, I would like to see good reasoning why this one singular term is not considered dynamic value, when everything else can be translated quite nicely, with these multilingual plugins. (On other site I have used Polylang, and it works nicely as long as we don’t try supporting anything fancy like we need to do with this client.)

    Thread Starter mikasolinum

    (@mikasolinum)

    Update
    I gave WPML another look, based on what you mentioned. And realized the “Theme and plugins localization” was showing 0 strings for Complianz, not because it wans’t supported, but because I had not scanned it. After completing scan, the WPML did offer me some good 1200+ new strings to translate, including “Always active”, and I could translate this string successfully from within WPML.
    If this was mentioned in some WPML tutorial, I did not see it, and for that I recommend updating this tip to official help, or if it is there already tap on your back for job well done and mark this as another user error.

    Plugin Contributor Jarno Vos

    (@jarnovos)

    Hi @mikasolinum,

    Thank you for getting back to us and sharing the solution, glad to hear you were able to resolve this already.

    I will make a note to add that to our WPML configuration article as a troubleshooting hint, this could definitely help other users experiencing a similar issue.

    Kind regards,
    Jarno

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

The topic ‘Not all strings appear translateable’ is closed to new replies.