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

Microsoft 365 email ticket font is broken #5157

Open
Milbong opened this issue Apr 30, 2024 · 1 comment
Open

Microsoft 365 email ticket font is broken #5157

Milbong opened this issue Apr 30, 2024 · 1 comment

Comments

@Milbong
Copy link

Milbong commented Apr 30, 2024

Used Zammad Version

6.3.0

Environment

  • Installation method: [source]
  • Operating system (if you're unsure: cat /etc/os-release ): ubuntu 22.04
  • Database + version: postgresql 14.11
  • Elasticsearch version: [7.17.20] Browser + version: [e.g. chrome 124.0.6367.63]

Actual behaviour

we using ticketing by connecting Microsoft 365 e-mail.

I would like to share a way to solve this problem as fonts are sometimes broken in emails coming through Korean.

setting-
image

problem-
image

clear-
image

The fonts of emails sent from Outlook Web are corrupted, but the fonts of emails sent from the app are not corrupted.
After viewing the email in HTML, it appears that there is a problem with the encoding method. How should I resolve this problem?

problem html tag-

Test mail
Ĺ×˝şĆŽ ¸ŢŔĎ

 

 

 

°¨ťçÇŐ´Ď´Ů. 

clear html tag-

Test mail

테스트 메일

 

 

 

 

감사합니다

plz help me..

thank you

Expected behaviour

clear-
image

clear text

Steps to reproduce the behaviour

  1. Write emails in Outlook web use korean
  2. send ticket
  3. check ticket

but outlook app is clear text

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes

@Milbong
Copy link
Author

Milbong commented Apr 30, 2024

clear tag
image

problem tag
image

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

No branches or pull requests

1 participant