Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add ability to encode header entries #108

Merged
merged 2 commits into from
May 27, 2023
Merged

add ability to encode header entries #108

merged 2 commits into from
May 27, 2023

Conversation

thoka
Copy link
Contributor

@thoka thoka commented May 21, 2023

Encode subject, if a feed contains non-ASCII characters.

thoka added 2 commits May 21, 2023 09:57
* add encodeHeader function to template
* update template to encode subject and tag in mail header
* add documentation to template
* adjust test for changed template
@skx
Copy link
Owner

skx commented May 21, 2023

This seems reasonable, and useful,, at a quick glance.

I'll test and merge in a day or two, but busy here just now.

Thanks for your contribution :)

@skx skx merged commit a4d049c into skx:master May 27, 2023
@visit1985
Copy link
Contributor

This breaks the format of non-atom feed subjects for me.

https://aws.amazon.com/about-aws/whats-new/recent/feed/

Any ideas? Thanks in advance!

@skx
Copy link
Owner

skx commented Jun 10, 2023

Confirmed, I see the same thing.

If there's no update from @thoka within the next week I'll have to revert, and see if there is a middle-ground.

@thoka
Copy link
Contributor Author

thoka commented Jun 13, 2023

Hm.

quotedprintable inserts soft line breaks (=\r\n), when line length exceeds 76 chars

Fixed in thoka@39de2c7

@visit1985
Copy link
Contributor

visit1985 commented Jun 13, 2023

Thanks @thoka. I can confirm that the fix works.

@skx
Copy link
Owner

skx commented Jun 18, 2023

Applied now, and released as release-3.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants