14 untranslatable language strings

14 untranslatable language strings

YoshidaMitsuhiro -
回帖数：8
Language pack maintainers的头像

There are 14 new language strings created under MDL-72509 that cannot be translated and committed, should I just leave them as they are?

[[MDL-72509] Move the participants filter UI from within core_user to a re-usable API - Moodle Tracker]
https://tracker.moodle.org/browse/MDL-72509

附件 amos.png
回复YoshidaMitsuhiro

Re: 14 untranslatable language strings

MartignoniNicolas -
Language pack maintainers的头像

I've experimented the same bug (?). I suspect this is because these strings were moved (strictly, they are not new).

Workaround: download your stage, empty it, then import your exported strings. This has enabled me to commit the French strings.

回复MartignoniNicolas

Er: Re: 14 untranslatable language strings

Zendegi UrzelaiIñigo -
Hi Nicolas,

I've tried to follow the workaround steps but haven't succeed, could you please add more details to help me detect what I'm doing wrong?

Thanks!

P.S.: The MDL that introduced this issue is already closed, so comments made after that maybe be gone after the radar of HQ, may it deserve to create another issue as a regression of MDL-72509?
回复Zendegi UrzelaiIñigo

Re: Er: Re: 14 untranslatable language strings

roggemanskoen -
Language pack maintainers的头像

You are right. I created a new one: https://tracker.moodle.org/browse/MDL-76232

I can confirm the workaround works.

Workaround: download your stage, empty it, then import your exported strings. This has enabled me to commit the French strings..

Since I've done it already, it's kind of difficult to replay and elaborate.

If you have the 14 translated strings in stage, you can download them there with one of the tools. Then you can delete all the strings in your stage, so it is empty. You can unzip the file with the downloaded strings and upload them again to your stage and commit. That should fix it.