GNU gettext - Bugs: bug #22975, xgettext: --add-comments ignores...
You are not allowed to post comments on this tracker with your current authentication level.
bug #22975: xgettext: --add-comments ignores comments not before strings
Submitter: | None | ||
Submitted: | Fri 18 Apr 2008 07:35:28 PM UTC | ||
Category: | Programmer tools | Severity: | 3 - Normal |
Item Group: | None | Status: | Fix Released |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Sun 20 Apr 2008 02:54:36 AM UTC, comment #1: |
Bruno Haible <haible> |
Fri 18 Apr 2008 07:35:28 PM UTC, original submission:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-01-04 | haible | Status | Fixed | Fix Released | |
2016-11-26 | haible | Category | None | Programmer tools | |
2008-04-20 | haible | Status | None | Fixed | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-4b48.
Corresponding source code
You expect --add-comments=TAG to extract all comment blocks
starting with TAG? That cannot work, as in PO files comments cannot
be standalone but are always attached to messages.
It's a documentation bug. I'm changing the --add-comments explanation
to be more explicit:
-cTAG, --add-comments=TAG place comment blocks starting with TAG and
preceding keyword lines in output file
-c, --add-comments place all comment blocks preceding keyword lines
in output file