GNU gettext - Bugs: bug #44098, Check strings for common problems
You are not allowed to post comments on this tracker with your current authentication level.
bug #44098: Check strings for common problems
Submitter: | Philip Withnall <drbob> | ||
Submitted: | Tue 27 Jan 2015 10:50:34 AM UTC | ||
Category: | Programmer tools | Severity: | 3 - Normal |
Item Group: | None | Status: | Fix Released |
Privacy: | Public | Assigned to: | ueno |
Open/Closed: | Closed |
Jump to the original submission
Fri 27 May 2016 09:09:32 AM UTC, comment #10: |
Daiki Ueno <ueno> |
Tue 03 Mar 2015 10:09:33 AM UTC, comment #9: Sorry for the delay. I've merged the current patch:
|
Daiki Ueno <ueno> |
Fri 06 Feb 2015 01:20:31 PM UTC, comment #8:
|
Philip Withnall <drbob> |
Fri 06 Feb 2015 01:18:17 PM UTC, comment #7: Thanks for the updated patch. I’ve taken a quick look over it and it looks good to me, though I’m no gettext reviewer.
|
Philip Withnall <drbob> |
Wed 04 Feb 2015 09:53:53 AM UTC, comment #6: To facilitate reviewing, I've posted the 2nd patch to the mailing-list (we should probably migrate to debbugs this year).
|
Daiki Ueno <ueno> |
Fri 30 Jan 2015 01:19:09 PM UTC, comment #5: Thanks for the review, they are all good points. I'll soon update the patch with tests. On error suppression, maybe we could reuse flags (the --flag option or "xgettext: ..." comment in the source code), though we should probaly name the warnings consistently like gcc's -W, e.g. no-*-check. |
Daiki Ueno <ueno> |
Thu 29 Jan 2015 10:42:40 AM UTC, comment #4: check_unicode_ellipsis(): this seems to check for ellipses only at the end of lines, whereas they can actually appear anywhere in a multi-sentence translatable string.
|
Philip Withnall <drbob> |
Thu 29 Jan 2015 08:33:53 AM UTC, comment #3:
|
Daiki Ueno <ueno> |
Wed 28 Jan 2015 08:56:10 AM UTC, comment #2: That sounds reasonable to me. I suggest the ultimate goal is to get the .pot file checked in `make check -C po`. |
Philip Withnall <drbob> |
Wed 28 Jan 2015 02:58:04 AM UTC, comment #1: Thanks, that's an interesting idea, but I don't think msgfmt is the right place to add those checks. The command is supposed to take a PO file rather than a POT file as its input, and it would be annoying if the warnings were issued when processing every PO file.
|
Daiki Ueno <ueno> |
Tue 27 Jan 2015 10:50:34 AM UTC, original submission:
It would be interesting if gettext could optionally run some tests on strings when it compiles a catalogue.
|
Philip Withnall <drbob> |
Depends on the following items: None found
Items that depend on this one: None found
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 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-01-04 | haible | Status | Fixed | Fix Released | |
2016-11-27 | haible | Category | None | Programmer tools | |
2016-05-27 | ueno | Status | In Progress | Fixed | |
Open/Closed | Open | Closed | |||
2015-01-29 | ueno | Attached File | - | Added 0001-xgettext-Support-message-syntax-checks.patch, #32936 | |
Status | None | In Progress | |||
Assigned to | None | ueno | |||
2015-01-27 | piotrdrag | Carbon-Copy | - | Added piotrdrag |
Powered by Savane 3.13-758e.
Corresponding source code
This was added in 0.19.5.