[micbar]

Backport of the translate() fix from #3789. Emails without a call to action (share expired, membership expired, ScienceMesh) got the .po header appended in every translated language, gotext returns it for an empty string.

Fixes #3830 on stable-7.2. Regression test with a German ShareExpired.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 4 complexity

Metric	Results
Complexity	4

View in Codacy

🟢 Coverage 68.42% diff coverage · +0.11% coverage variation

Metric	Results
Coverage variation	✅ +0.11% coverage variation (-1.00%)
Diff coverage	✅ 68.42% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (6f49f86)	Report Missing	Report Missing	Report Missing
Head commit (ce0d7ce)	82088 (+5)	19059 (+95)	23.22% (+0.11%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#3833)	19	13	68.42%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[micbar]

@v-scharf This is a possible backport, the problem is described in #3830

[v-scharf]

@micbar @schweigisito @Svanvith
here I described process:

• I put label backport-required to the issue ([Bug]: German translation metadata (PO header) appended to share revocation email body #3830 in this case) -> Issue appears in the board OpenCloud Team Board (view)
• I link issue with PR in main and PR in stable (if we have) and set the status, and assign someone to handle the backport

[micbar]

This is already the backport PR