Re: Enabling $rfc2047_parameters by default

2022-01-10 Thread Kevin J. McCarthy
On Mon, Jan 10, 2022 at 06:08:12PM -0600, Derek Martin wrote: On Sat, Jan 08, 2022 at 02:46:48PM -0800, Kevin J. McCarthy wrote: I'm thinking about enabling $rfc2047_parameters by default, and would like to hear any counter-arguments against this. I believe the original argument against was th

Re: Enabling $rfc2047_parameters by default

2022-01-10 Thread Derek Martin
On Sat, Jan 08, 2022 at 02:46:48PM -0800, Kevin J. McCarthy wrote: > I'm thinking about enabling $rfc2047_parameters by default, and would like > to hear any counter-arguments against this. I believe the original argument against was that doing so violates the RFCs, and therefore potentially obscu

Re: Enabling $rfc2047_parameters by default

2022-01-08 Thread Steffen Nurpmeso
Kevin J. McCarthy wrote in : |I'm thinking about enabling $rfc2047_parameters by default, and would |like to hear any counter-arguments against this. | |Here we are in 2022, yet I still occasionally receive tickets, or most |recently even a merge request (!154), about this. Obviously some