http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5743
------- Additional Comments From [EMAIL PROTECTED] 2007-12-07 23:42 ------- Suggestion on enhanced syntax for ok_locales that I think solves the chicken and egg problems, and eliminates the need for not_ok_locales. 1. Support ok_locales with the current syntax in the following way: eliminate the current ok_locales list and replace it with the list in the current statement. This will correctly allow a ok_locales in user_prefs to override a global ok_locales statement. 2. Add a new parameter syntax to ok_locales: a. Locale identifiers preceeded by a + or - character b. A Meta-locale of "all" preceeded by a + or - character. If the first parameter encountered in ok_locales is NOT preceeded by a + or - character, original syntax parsing (1) is used. If the first locale name IS preceeded by a + or - character, new syntax parsing (2) is used. If new syntax parsing is used and a locale name is found without a + or - sign, treat it as having an implicit + sign. Alternately, give a syntax error for ambiguous option, mentioning the locale in question in the error message. Note that the meta-locale of +all or -all can potentially occur at any point in the list, although it isn't real practical as anything other than the first locale. (Note this same enhanced syntax can and probably should be used for ok_languages for consistency of syntax and function.) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
