Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When sending emails with multi-word non-ASCII subjects (Korean, Japanese, Chinese, etc.), spaces between words are lost. For example, "가장 높은 산, 가장 긴 강" becomes "가장높은산,가장긴강".
The problem is
message/compose.gowhere each non-ASCII word is encoded separately, producing adjacent encoded-words like=?utf-8?q?word1?= =?utf-8?q?word2?=.Per RFC 2047 Section 6.2, email clients ignore whitespace between adjacent encoded-words, causing spaces to disappear.
This commit fixes this issue by grouping consecutive non-ASCII words before encoding them as a single encoded-word. This preserves spaces inside the encoding. Also added line folding at 77 characters for both ASCII and non-ASCII text per RFC 822/2047, and preserved exact whitespace (trailing/multiple spaces) which was previously normalized.