[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-gettext] [bug #44098] Check strings for common problems
From: |
Philip Withnall |
Subject: |
[bug-gettext] [bug #44098] Check strings for common problems |
Date: |
Tue, 27 Jan 2015 10:50:34 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 |
URL:
<http://savannah.gnu.org/bugs/?44098>
Summary: Check strings for common problems
Project: GNU gettext
Submitted by: drbob
Submitted on: Tue 27 Jan 2015 10:50:34 GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
It would be interesting if gettext could optionally run some tests on strings
when it compiles a catalogue.
There are some here, written as a Makefile, but they could be ported to
gettext easily enough:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-session/trunk.13.04/view/head:/tests/Makefile.am.strings
For example, they check that a Unicode ellipsis character has been used
instead of three periods in a row, that ASCII quotation marks aren’t used,
and that there are no spaces before ellipses.
These rules are somewhat style-specific, so should not be enabled for all
projects. Perhaps they could be enabled individually as a series of checker
options?
e.g.
msgfmt -Wunicode-ellipses -Wspace-before-ellipsis -Wascii-quotes …
This was originally a bug against gnome-common, but we decided it wasn’t the
right place to implement it:
https://bugzilla.gnome.org/show_bug.cgi?id=689602.
_______________________________________________________
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,
Philip Withnall <=