<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Tooling allows (and thus code has) duplicate string entries for translation" href="https://bugs.documentfoundation.org/show_bug.cgi?id=109258#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Tooling allows (and thus code has) duplicate string entries for translation" href="https://bugs.documentfoundation.org/show_bug.cgi?id=109258">bug 109258</a> from <a class="email" href="mailto:cloph@documentfoundation.org" title="Christian Lohmaier <cloph@documentfoundation.org>"> Christian Lohmaier</a> <pre>re fixing for 5.4 I'll just add what I wrote in mail: As master branch with gettext migration doesn't have duplicate (non-unique strings in terms of po-format), and that fixing it for 5.4 would be a break of string freeze (and the problem is not in translations themselves, but just when updating against latest templates, which now after string freeze should be rare exception) I consider this wfm/wontfix for the 5-4 branch. An easy workaround exists (running msguniq over the templates), the code itself doesn't care about duplicates (I think it is first-match-wins, but might be non-deterministic if there are indeed dupes) and pootle based translations are already cleared off the duplicates (and even if there were could be cleaned up using the same msguniq call). Happy to wait with tagging for 5.4.1 rc2 until Thu evening or even Friday. Not sure Whether the Commit to the branch is a intermediate or already the fully completed version.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>