Hi everyone, There’s a bug open in gettext at the moment about checking strings for common problems: https://savannah.gnu.org/bugs/index.php?44098 https://lists.gnu.org/archive/html/bug-gettext/2015-02/msg00002.html This was previously open against gnome-common[1], and is based on the automake fragments written by Ted Gould for some Ubuntu stuff. Does anybody have any feedback on this idea? Or ideas for further checkers to add to gettext? The checkers would not be enabled by default, but could be enabled by developers on a case-by-case basis, depending on what style they want to enforce on their translatable strings. The checks we have so far: • Use of Unicode ellipsis (‘…’) instead of ASCII (‘...’). • No space before an ellipsis (‘…’ rather than ‘ …’). • Use of Unicode quotation marks (‘“’ rather than ‘"’, etc.). I’m suggesting that checks should: • Be an absolute rule: there should be no situations where a string should legitimately fail the check. • Catch common errors; it’s not worth trying to catch uncommon ones. • Enforce a particular style on a project’s strings, and checks can exist which use different style guides. Philip [1]: https://bugzilla.gnome.org/show_bug.cgi?id=689602
Attachment:
signature.asc
Description: This is a digitally signed message part