Raul Dias writes: > On Wed, 2007-02-21 at 17:27 +0100, Justin Mason wrote: > > Raul Dias writes: > > > On Wed, 2007-02-21 at 15:29 +0100, Justin Mason wrote: > > > > actually I think this is already implemented in 3.2.0 -- see > > > > http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4636 for details. > > > > > > Nice. This patch solves the message part problem. > > > > > > With this, rules can be written in Unicode too. > > > A final change would be to let rules be written into other charserts. > > > > > > Rule files are read separated. A easy implementation would be to add a > > > file_charset option. This option will advice the charset used by the > > > rule file like iso-8859-15 and be converted internally to unicode too if > > > and only if (IMO) normalize_charset option is set to 1. > > > > I think I prefer the current model, where rules are UTF-8, I'm > > afraid ;) > > Just to get this straight. > > All rules are considered UTF-8 (no difference for ascii ones)? > Is this on 3.2 only or 3.1 too? > > I have assumed that it would be iso-8859-1 so far.
With the "normalize_charset" code active, it's UTF-8. (iirc) --j.
