4.x: Fix parsing of PO files without empty lines #296
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves an issue that was brought to our attention in wp-cli/i18n-command#393
Turns out that
msgfmt
doesn't like empty lines between translations when merging PO files, and instead adds empty comments.So a file like this:
Gets turned into this:
As per the spec, whitespace between entries is optional. However, Gettext v4 doesn't parse these files correctly when they look like this.
This PR addresses that.
In the WP-CLI i18n command we currently rely on Gettext v4 because of PHP version requirements, so I hope this bugfix gets accepted still.