Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'msgid' and 'msgstr' entries do not both end with '\n' #365

Open
mauritsvanrees opened this issue Jul 12, 2022 · 0 comments
Open

'msgid' and 'msgstr' entries do not both end with '\n' #365

mauritsvanrees opened this issue Jul 12, 2022 · 0 comments

Comments

@mauritsvanrees
Copy link
Member

When in the locales directory, I check all po files with msgfmt, redirecting stderr/stdout to a file so I can properly grep for a fatal error:

$ for i in */*/*.po; do msgfmt -c $i; done &> x
$ grep -B1 fatal x
ca/LC_MESSAGES/plone.po:10856: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 1 fatal error
--
de/LC_MESSAGES/plone.po:14240: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 3 fatal errors
--
it/LC_MESSAGES/plone.po:13549: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 3 fatal errors
--
ru/LC_MESSAGES/plone.po:13549: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 1 fatal error
--
sl/LC_MESSAGES/plone.po:13513: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 1 fatal error
--
zh_TW/LC_MESSAGES/plone.po:13512: 'msgid' and 'msgstr' entries do not both end with '\n'
msgfmt: found 2 fatal errors

There are various warnings as well. But the fatal errors could mean that Plone fails to parse some po files at startup, causing missing translations.

This reminds me, it might be nice to have a few checks using GitHub actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant