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.
Hi,
I found that multiline message ids aren't handled correctly. Let's say we have a translation string like this:
then the PO file will be something like:
and that's not the correct syntax AFAIK. In fact, poedit truncates the msg id to "Info". The correct output should be
So, this PR is my take on this problem: with this I am able to export multiline translation strings as POT file, translate 'em with poedit and parse the resulting PO file back with pottery.
I'll be the first to say that
fmt-msg-id
is a terrible name for a function, but I'm not too inspired tonight, apologies. Also, the choice to usecl-format
may be too brave but, while the format string seems some sort of line noise, I fear that any more verbose alternative would require the same mental effort. Anyway, I don't have strong feelings towardscl-format
, so I can change that eventually.