-
Notifications
You must be signed in to change notification settings - Fork 484
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
Inappropriate converting of umlauts in subject #2965
Comments
Are you using modern Microsoft OAuth IMAP authentication or |
No to both. |
Try to add the following to .env file and clear cache:
|
I tried but the issue is still there |
Reproducible in the freescout demo if that helps |
It seems the falsy conversion takes place here The issue is gone when I change this line to
But I don't know if this is a suitable solution in general. |
Now |
Hello.
We got a strange behaviour reported when someone is trying to copy the subject of a conversation/email (Schadensmeldung FÜ230414439), paste it somewhere else inside the browser (atleast in latest chrome) and try to delete (backspace) the character Ü, which gets not deleted but instead, turns into an U.
The header information seems to be correct
Subject: =?UTF-8?Q?Schadensmeldung_F=C3=9C230414439?=
The website https://unicodelookup.com/ reveals that the Ü is some sort of a combined character (?)
combined Ü
manual typed Ü
This is a problem for us since we sometimes use the subject (or parts of it) to compare or search things in our database where things usually correct encoded/converted.
Thanks in advance.
The text was updated successfully, but these errors were encountered: