Not being translated with multilingual plugin

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author r-a-y

    (@r-a-y)

    At the moment, you need to manually translate BP Follow with the bundled .pot file:
    https://raw.githubusercontent.com/r-a-y/buddypress-followers/master/languages/bp-follow.pot

    BP Follow currently supports the following languages:
    https://github.com/r-a-y/buddypress-followers/tree/master/languages

    If you need help translating, let me know and I’ll try to point you in the right direction.

    I don’t have any experience using polylang, so I can’t say for certain what the problem is.

    Thread Starter miguelcortereal

    (@miguelcortereal)

    It looks like I didn’t express myself clear enough.

    Translating BP Follow into a new language isn’t the issue here, in fact if you want to I can send you the pt_PT .mo and .po files to add to plugin’s language folder.

    Unlike all plugins and theme, the issue is the multilingual functionality isn’t working for BP Follow plugin, or better said, no matter how many language files are at language folder, they just never get read and thus it keeps displaying always in English.

    Polylang plugin does pretty much what WPML plugin does.

    Plugin Author r-a-y

    (@r-a-y)

    in fact if you want to I can send you the pt_PT .mo and .po files to add to plugin’s language folder.

    Would much appreciate it if you are able to send your translation files. Would be great if you could translate the latest strings in the bleeding version as linked to above.

    As for Polylang, I took a quick look at Polylang’s documentation and I already follow what they recommend:
    https://polylang.wordpress.com/2014/08/15/dont-take-any-action-before-plugins_loaded-is-fired/

    I don’t have time to figure out what the issue is at the moment. If you are able to pinpoint what the problem is, let me know.

    Thread Starter miguelcortereal

    (@miguelcortereal)

    I think I have it figured out, at least translations started to work now.

    You started to use contextual strings and when you do that the source keywords list that goes at Poedit gets more complex.

    The catch seems to be every _x string function for which is necessary to use _x1.2c source keyword to have Poedit properly recognizing each contained string.

    So, it should be included at Catalog –> Properties –> Sources Keywords :

    __
_e
_x1,2c

    Your .pot file need this update.

    The updated pt_PT translation from the bleeding version at Github can be downloaded here.

    Plugin Author r-a-y

    (@r-a-y)

    Glad that you figured out the problem.

    The .pot file does support a “X-Poedit-KeywordsList” header, but the script I use to generate the .pot file doesn’t add this header.

    In the meantime, for any one else reading this thread, I would recommend reading this great PoEdit guide:
    https://www.cssigniter.com/ignite/wordpress-poedit-translation-secrets/

    Thanks for providing your translations, miguelcortereal. I’ll add them in to the bleeding version in a bit.

    Thread Starter miguelcortereal

    (@miguelcortereal)

    There’s a slight detail that I need to correct:

    Use:

    __
_e
_x:1,2c

    Instead of:

    __
_e
_x1,2c

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Not being translated with multilingual plugin’ is closed to new replies.