[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-gettext] [bug #44098] Check strings for common problems
From: |
Daiki Ueno |
Subject: |
[bug-gettext] [bug #44098] Check strings for common problems |
Date: |
Wed, 04 Feb 2015 09:53:53 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 |
Follow-up Comment #6, bug #44098 (project gettext):
To facilitate reviewing, I've posted the 2nd patch to the mailing-list (we
should probably migrate to debbugs this year).
https://lists.gnu.org/archive/html/bug-gettext/2015-02/msg00001.html
Changes from v1 are:
- recognize "xgettext: no-*-check" comment in source code
- add test case
- refactor quoted segment scanning into a separate file
which was done in a separate commit:
http://git.sv.gnu.org/cgit/gettext.git/commit/?id=01658057
- refactor syntax check function invocation
I'm a bit reluctant to support multi-sentence strings at the moment, since the
original tools (po/Rules-quot and the indicator-applet's Makefile.am snippets)
only consider single-sentence strings. So that part has not changed since
v1.
Also, suppression of checks with a command-line option is not implemented
(yet) for implementation reasons (currently the --flag option only accepts
*-format flags).
Anyway, further reviewing and suggestions for further checks would be
appreciated.
Here are some I have in mind:
- check if a message is/isn't ends with "."
- check if a message is/isn't capitalized
- suggest two spaces after "." for multi-sentence strings
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44098>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug-gettext] [bug #44098] Check strings for common problems,
Daiki Ueno <=