I am trying to implement this (it seemed like a good way to start developing on SA).
The strait forward way was to just update the $lang variable in
Parser.pm, but the $lang is obeviously set before the parsing of
$self->{config_text} begins. There is also a nother problem. The
userprefs file is parsed as the last one which makes it hard to select
the right "lang xx" configuration lines.
The problem could be solved by parsing the 30_text_xx.cf files last,
but I dont if that creates other problems.
---------- Forwarded message ----------
From: Theo Van Dinter <[EMAIL PROTECTED]>
Date: Wed, 1 Sep 2004 11:04:13 -0400
Subject: Re: How do I use the localized reports
To: [email protected]
On Wed, Sep 01, 2004 at 10:58:50AM -0400, Matt Kettler wrote:
> I for one disagree since nearly every other unix application in the world
> uses LANG it makes sense to be consistent with the defacto standards.
> Creating our own setting merely breaks expected behavior.
Yes, but what if people use spamd? LANG for spamc is irrelevent, and the LANG
for spamd is a global default.
What I would guess is that the code should use LANG, but a configuration
option "use_language" (or something) would reset LANG appropriately.
Therefore "spamassassin" and "sa-learn" can do the right thing, and spamd
would have an option to change LANG at run-time.
--
Randomly Generated Tagline:
"On the big starship of life, I think I'd be the morale officer..." - Theo
--
Morten Isaksen
http://www.aub.dk/~misak/
pgpsRwMlBlNBN.pgp
Description: PGP signature
