Re: [bug-gettext] Debian Bug#872869: msgfmt: trailing null bytes in header's msgstr

Hi Daiki, > >> $ msgunfmt /usr/share/locale/pl/LC_MESSAGES/gettext-runtime.mo | msgfmt - > >> $ i18nspector messages.mo > >> E: messages.mo: invalid-mo-file unexpected null byte in msgstr > Although it was reported against an unreleased version, can we have a > test case for this to prevent

Re: [bug-gettext] Debian Bug#872869: msgfmt: trailing null bytes in header's msgstr

Bruno Haible writes: >> $ msgunfmt /usr/share/locale/pl/LC_MESSAGES/gettext-runtime.mo | msgfmt - >> $ i18nspector messages.mo >> E: messages.mo: invalid-mo-file unexpected null byte in msgstr > > Thanks for this report! Fixed through > http://git.savannah.gnu.org/gitweb/?p=gettext.git;a=co

Re: [bug-gettext] Debian Bug#872869: msgfmt: trailing null bytes in header's msgstr

Hi Santiago, > One of them is that now glibc does not build because the gettext tests > still expect the POT-Creation-Date header to be there. > This has been reported here: > > https://sourceware.org/bugzilla/show_bug.cgi?id=21508 We're discussing this at .

[bug-gettext] Debian Bug#872869: msgfmt: trailing null bytes in header's msgstr

Dear gettext maintainers: I applied commit d13f165b8370 to the Debian gettext package, as suggested by Bruno Haible, and several things happened. One of them is that now glibc does not build because the gettext tests still expect the POT-Creation-Date header to be there. This has been reported he