Re: Question about RFC-2047 (utf-8 encoding in message headers)

[Eugen Stan]

Hi,

On 04.01.2023 09:33, Benoit TELLIER wrote:

Hello Firstie Lastie,

If doing so:

  - 1. do not come at a big performance price and
  - 2. do not compromise overall correctness

Then I do believe that such lenient behavoir contribution would be welcome.

Don't hesitate to open a pull request regarding this on github.

Regards,


Is this really necessary?
How often does this situation arise in practice?

I think this would complicate the parsing logic.
I personally am Ok with this if it's an OPT-IN strategy and is added 
with tests.


Even so, I am a bit reluctant to add more code to maintain unless there 
is a good reason.


Thanks,
Eugen

Re: Question about RFC-2047 (utf-8 encoding in message headers)

[Firstie Lastie]

Thanks, will do!

On Wed, Jan 4, 2023 at 2:33 AM Benoit TELLIER  wrote:

> Hello Firstie Lastie,
>
> If doing so:
>
>   - 1. do not come at a big performance price and
>   - 2. do not compromise overall correctness
>
> Then I do believe that such lenient behavoir contribution would be welcome.
>
> Don't hesitate to open a pull request regarding this on github.
>
> Regards,
>
> Benoit
>
> On 03/01/2023 22:16, Firstie Lastie wrote:
> > Hello,
> >
> > I've noticed that when I have a message header (for example 'subject')
> > which has a mixture of ascii and utf-8 encoded-text, it requires a space
> > for the encoded text to be properly decoded.  This follows the spec,
> which
> > says:
> >
> > "IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by
> an RFC
> > 822  parser."
> >
> > and RFC-822 states:
> >
> > "Atoms ...  are delimited by the self-delimiting symbols and by
> > linear-white-space."
> >
> > I'm wondering if the support could be expanded so that subjects which DO
> > NOT contain the mandatory delineating space would also be supported.
> >
> > Cheers,
> > fl
> >
>

Re: Question about RFC-2047 (utf-8 encoding in message headers)

[Benoit TELLIER]

Hello Firstie Lastie,

If doing so:

 - 1. do not come at a big performance price and
 - 2. do not compromise overall correctness

Then I do believe that such lenient behavoir contribution would be welcome.

Don't hesitate to open a pull request regarding this on github.

Regards,

Benoit

On 03/01/2023 22:16, Firstie Lastie wrote:

Hello,

I've noticed that when I have a message header (for example 'subject')
which has a mixture of ascii and utf-8 encoded-text, it requires a space
for the encoded text to be properly decoded.  This follows the spec, which
says:

"IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by an RFC
822  parser."

and RFC-822 states:

"Atoms ...  are delimited by the self-delimiting symbols and by
linear-white-space."

I'm wondering if the support could be expanded so that subjects which DO
NOT contain the mandatory delineating space would also be supported.

Cheers,
fl

Question about RFC-2047 (utf-8 encoding in message headers)

[Firstie Lastie]

Hello,

I've noticed that when I have a message header (for example 'subject')
which has a mixture of ascii and utf-8 encoded-text, it requires a space
for the encoded text to be properly decoded.  This follows the spec, which
says:

"IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by an RFC
822  parser."

and RFC-822 states:

"Atoms ...  are delimited by the self-delimiting symbols and by
linear-white-space."

I'm wondering if the support could be expanded so that subjects which DO
NOT contain the mandatory delineating space would also be supported.

Cheers,
fl