• in includes/functions.php (line 205-224)
    The translations attempt use context translation, it should be using `_x() instead of __()
    __(….. => _x(….. for context translation`

    Besides, in your translation .po file, adding the tag “msgctxt” in order to use context translation, for example

    msgctxt "Initial payment in cost text generation."
    msgid "The price for membership is <strong>%s</strong> now"
    msgstr "something you want to translate<strong>%s</strong>"

    And notes for translation using context, my case is using POEDIT,
    similar terms seems confusing the parsed result, I didn’t detailedly confirm whether it is compiled MO file problem or the translation.
    if one msgctxt is using “Initial payment in cost text generation.”
    the other one using “Initial payment in cost text generation XXX”
    It will not get any translation in the result.

    So, I suggest before updating to next version, other context in line 205-217 have to be adjusted and tested.

    Hope it can help some people to save time.

    http://wordpress.org/plugins/paid-memberships-pro/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter 西門 正 Code Guy

    (@simongcc)

    another location is adminpages.php (line 24, 25)

    Membership Levels =>
    __( "Membership Levels", "pmpro" )

    so that it will not keep as “Membership Levels” while other words get tranlsated.

    Hey there,

    Thanks, I’ll make sure Jason, our lead developer, knows about this and we’ll try to get it out with the next version!

    Jess

    I was confused about this, too.
    Lots of ‘_x’ used, but I could not find any “msgctxt” in the pot file.

    Fix in the next release is really good news 🙂

    Thread Starter 西門 正 Code Guy

    (@simongcc)

    Thanks for your reply, I have finished almost 50% translation by now.
    And I have found more translation bugs, I will post here for everyone reference.

    Thanks again for making such a great tools.

    Jessica Oros

    (@jessica-o)

    Marking this as resolved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Translation bugs report’ is closed to new replies.