-
Notifications
You must be signed in to change notification settings - Fork 315
fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_5601-1989 #12654
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
Open
ChristophWurst
wants to merge
8
commits into
main
Choose a base branch
from
fix/imap/korean-windows-encoding
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1b7648d
fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_5601-1989
ChristophWurst f203cdf
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst 03d0f31
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst e9c14b8
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst 432207f
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst d6b9aa9
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst a4d64f9
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst b758b49
fixup! fix(imap): handle korean Windows encoding ks_c_5601-1987/ks_c_…
ChristophWurst File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After catching ValueError for an invalid charset name, the code comment says it should “fall through to auto-detection”, but later
$normalizedCharsetis recomputed from the original (still-invalid)$charsetand passed tomb_convert_encoding()/iconv()again. This prevents the intended autodetect fallback and guarantees aServiceExceptionfor invalid charset tokens even when mbstring could detect/convert the bytes. Consider treating an invalid/empty charset asnull(or setting a flag) so the later conversion uses autodetection instead of retrying the invalid name.