I have attached the patch. I removed the common part of the charset preserving code from GenericListServ and added it to AbstractRedirect. The prefix functionality now works correctly with non-ASCII characters. (Assuming that the prefix is ASCII only.)
Because I had to change that part anyway, I modified AbstractRedirect to not change the subject if not necessary. So Forward doesn't eat non-ASCII characters now. (But I haven't changed the null / empty string usage.) ----- Original Message ----- From: "Hontvari Jozsef" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Saturday, June 28, 2003 5:52 PM Subject: Re: AstractRedirect and non-ascii characters > From: "Noel J. Bergman" <[EMAIL PROTECTED]> > > > The root of the problem is the same as was in GenericListserv. > > > > (a) Would you like to submit a patch based upon your previous work? > > > yes. I also had an enhancement idea to the current algorithm. > > > IMO, you can submit it for AbstractRedirect. Eventually, I would expect > > either to see more mailets that resend mail to inherit from > > OK, then I'll move the code from GenericListServ to the public interface of > AbstractRedirect. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
AbstractRedirectNonAsciiChars.patch
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
