Translation problem

  • Resolved OlafKS

    (@olafks)


    10 years, 11 months ago

    Hi ??
    First of all, thanks for great plugin!
    For now I’m trying to translate it, using .po and .mo files, that I found in Languages folder, but it seems, that these files are bit broken ??
    For example – when I’m translating string “%d Points”, I see translated version at the frontend.
    but when I’m translating string “Filter:” for example, at the frontend it remains in English.
    Could you check this problem, please? ??

    P.S. If you need it – I could send you russian translation when I’m done.

    https://www.ads-software.com/plugins/badgeos/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Michael Beckwith

    (@tw2113)

    The BenchPresser

    Which version are you on? I can see if we missed any spots for translation sometime soon, but it may not be right away today. If you know what component it’s coming from then I can target that area specifically and make sure it gets into the next version as well.

    Thread Starter OlafKS

    (@olafks)

    badgeos 1.3.5
    Well.. about components… For example form, that is generated by [badgeos_achievements_list] shortcode. There are no Show Details \ Hide Details strings, “Required Steps”, Filter, search – are not working. All\Completed\not completed are missing…
    Some strings are working, but nearly half of them are not working or missing.
    I would be very grateful, if you could fix this. The most important part is frontend ofcourse. I have no problems with english, so admin area is not so important, but frontend is important ??
    And if you need this translation, then I need to translate admin area too, so you need to check it too. ??

    Michael Beckwith

    (@tw2113)

    The BenchPresser

    Ahh, yes, I can see where we are definitely missing some gettext spots.

    My question at this point is this. How essential is it to get these spots done ASAP, versus what could technically wait a week or two more?

    The reason I ask is because we’re most of the way through the 1.4.0 release, but still have some stuff to finish up. We want it out pretty soon though. If you’re able to wait for that much, then I can make sure to go through everything and make sure we didn’t miss any string translations and then you could work from the newest version.

    Otherwise, I can try to get you a .pot file from the current version with these spots patched, and send that to you. However given new features coming in, it will be worth waiting if you can. We will also happily accept the .po/.mo files and include them for everyone once done.

    Thread Starter OlafKS

    (@olafks)

    Wow! no-no-no, it is not so urgent, I’m really able to wait for week or two, it’s not a problem ??
    Thank you for quick response, you are really cool ??

    Michael Beckwith

    (@tw2113)

    The BenchPresser

    I have combed the php files and gotten every spot I can find. Still need to discuss handling a bit of text in javascript, but we’re looking good for this coming up.

    Michael Beckwith

    (@tw2113)

    The BenchPresser

    Marking resolved, we have it documented and “issued” in GitHub for tracking.

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