[Bug 1547166] Belarusian translati on plural form change request
| Newsgroups | gmane.linux.redhat.internationalization |
|---|---|
| Message-ID | <[email protected]> |
https://bugzilla.redhat.com/show_bug.cgi?id=1547166 Viktar Siarheichyk <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |NEW Resolution|NOTABUG |--- Keywords| |Reopened --- Comment #8 from Viktar Siarheichyk <[email protected]> --- Apparently not all is OK. Even though zanata web UI presents 3 placeholders to translate plural forms, zanata-cli pull returns a misformatted po file: [WARN] Marking as fuzzy: too many plural forms for text flow: resId=1273d0db45545a9b269637da4d9d2889, doc=anaconda [WARN] Marking as fuzzy: too many plural forms for text flow: resId=0a7d55be9d12a369a6a8da0fb517fba4, doc=anaconda [WARN] Marking as fuzzy: too many plural forms for text flow: resId=6cc492bd732baf97c15d577104134a1b, doc=anaconda [WARN] Marking as fuzzy: too many plural forms for text flow: resId=e4c936ce2cbdbab6c303bdd0a6166ee8, doc=anaconda because there are several msgstr[3] entries present whereas nplurals=3 in the received .po file. When I remove the excess msgstr[3] entries and do zanata-cli push again, it merges with the existing "invalid" .po on the server and nothing changes. I seem to need a person with admin rights to clean up the be.po for anaconda on the server or whatever file or DB is under the hood there. Besides I messed up with the .po header trying to update it, instead of changing the initial 3 lines: # Belarusian translations for anaconda. # Copyright (C) 2018 Red Hat, Inc. # This file is distributed under the same license as the anaconda package. - it added my changes between the contributor copyright strings while preserving the original boilerplate I intended to change. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ trans mailing list -- [email protected] To unsubscribe send an email to [email protected]