Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Use correctly-encoded email headers for names with non-ASCII characters#54

Merged
derrickstolee merged 3 commits intogitgitgadget:mastergitgitgadget/gitgitgadget:masterfrom
dscho:non-ascii-ccdscho/gitgitgadget:non-ascii-ccCopy head branch name to clipboard
Dec 26, 2018
Merged

Use correctly-encoded email headers for names with non-ASCII characters#54
derrickstolee merged 3 commits intogitgitgadget:mastergitgitgadget/gitgitgadget:masterfrom
dscho:non-ascii-ccdscho/gitgitgadget:non-ascii-ccCopy head branch name to clipboard

Conversation

@dscho
Copy link
Member

@dscho dscho commented Dec 21, 2018

I ran into this issue a couple times when Cc:ing Ævar: if the Cc: header contains unencoded non-ASCII characters, the Git mailing list will simply reject that mail.

So let's encode those characters (using nodemailer's internal encodeWords() function).

This fixes #29.

Apparently, VS Code's internal formatting interferes with TSLint's
(resulting in the formatting seemingly reverting and then re-reverting
within half a second upon save). So let's disable VS Code's.

While at it, also define the alignment rules.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
... according to the new rules.

This (huge) commit best viewed with --color-words.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho dscho requested a review from derrickstolee December 21, 2018 23:57
@dscho
Copy link
Member Author

dscho commented Dec 21, 2018

Please note that this PR is based on #53, so that one should be merged first.

When sending mails, the From: or Cc: headers can only contain ASCII
characters. Any non-ASCII characters need to be encoded, otherwise the
emails will be rejected by the Git mailing list.

With this change, the test now also finally learns to test inserting Cc:
lines in the GitGitGadget mode (rather than testing the non-GitGitGadget
one).

This fixes gitgitgadget#29

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho
Copy link
Member Author

dscho commented Dec 22, 2018

@slavicaDj this PR, once merged, should unblock you.

@derrickstolee derrickstolee merged commit 8289922 into gitgitgadget:master Dec 26, 2018
@dscho dscho deleted the non-ascii-cc branch December 26, 2018 17:13
@dscho
Copy link
Member Author

dscho commented Dec 26, 2018

@slavicaDj this PR, once merged, should unblock you.

There you go!

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.

Encode the Cc: header correctly

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.