Some strings are not localized with Loco Translate

  • Resolved Number One Fan

    (@lubomir3000)


    7 years, 1 month ago

    Using Loco Translate almost all of the localized strings are localized but the error messages on the Login/Register forms are not. I’ve configured all settings of Loco correctly, the srtings in question are shown in Loco’s plugin translation screen as having existing translation. One such string is “ERROR: Password must be 7 characters or more.”
    I tested that behaviour with clean install of WordPress with only UsersWP and Loco Translate as plugins.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support alexrollin

    (@alexrollin)

    Loco translate does not recognize some language strings. We recommend using PoEdit instead.

    I verified that the .po file contains the translation of the string in question. The problem is related to the discovery of that string as for me. Can you confirm that you verified that the sring “ERROR: Password must be 7 characters or more.” is properly translated on your site?

    Plugin Contributor Paolo

    (@paoltaia)

    Hi,

    did you follow the documentation: https://wpgeodirectory.com/docs/translate-core/?

    That’s for GeoDirectory, but the process is identical.

    If yes, please open a support topic in our forum where we can help further. https://userswp.io/support/

    Thanks

    Thread Starter Number One Fan

    (@lubomir3000)

    From the documentation I got the idea that the problem may be is the directory of the .po files – they were placed in the custom directory …/wp-content/languages/loco/plugins. If the .po files are placed in …/wp-content/languages/plugins the localized string are shown correctly. However it more of workaroud for me, because using the custom “loco” directory is easier to track my own translations.

    Plugin Contributor Paolo

    (@paoltaia)

    Honestly I don’t know why the translation works when putting the file where it should and not when placing in the loco folder.

    I’m sorry, but that’s a support question for Loco authors. We already follow WordPress best practices for handling translations.

    Thanks

    Thread Starter Number One Fan

    (@lubomir3000)

    Loco is the only free alternative to WPML for translation. I honestly don’t know why you marked that topic as resolved

    Plugin Contributor Paolo

    (@paoltaia)

    Because our plugin works if you follow our documentation. So the topic is resolved for us.

    The problem is with Loco plugin, not GeoDirectory and we cannot fix 3rd party plugins.

    Thanks

    “Loco is the only free alternative to WPML for translation.”

    You only need WPML if you want a multi-lingual site. Loco Translate does not work for multi-lingual site.
    If you just want to translate to another language, the best free option is PoEdit.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Some strings are not localized with Loco Translate’ is closed to new replies.