Closed JiechengZhao closed 5 months ago
I'll add that later this week.
My manual https://www.gnu.org/software/gettext/manual/gettext.html#PO-Files (or at least not in the obvious section. didn't read anything about msgmerge yet) did not include that syntax, but if POEdit does, we should add it too. That should be easy, just adding this case in the PO-parser.
I'll add that later this week.
My manual https://www.gnu.org/software/gettext/manual/gettext.html#PO-Files (or at least not in the obvious section. didn't read anything about msgmerge yet) did not include that syntax, but if POEdit does, we should add it too. That should be easy, just adding this case in the PO-parser.
I guess the gettext
manual missed it in the PO files description. It is in the utils and the manual mentioned it here: https://www.gnu.org/software/gettext/manual/gettext.html#Message-selection-4 . I can only use search to find that. It's not even mentioned in all other utils. :scream: .
Sorry, forgot about this. The parser should now just drop them.
`lake exe i18n --export-json
failed on https://github.com/JiechengZhao/NNG4/commit/d4d1e19f13f58263df5790c33dd6621d9aac0b2a .The content is
#~
is generated bymsgmerge
(gettext) when it finds that an old script does not match or only fuzzily matches the current key. Deleting this part is okay, but since this is a common behavior in gettext, adding support for it would be good.