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

Japanese font rendering issue #1637

Closed
christophe-f8 opened this issue Jul 25, 2018 · 4 comments
Closed

Japanese font rendering issue #1637

christophe-f8 opened this issue Jul 25, 2018 · 4 comments

Comments

@christophe-f8
Copy link

Wire version: 3.2.2860
Wire for web version: 2017.07.16.1405
Operating system: Windows 10

The rendering of Japanese is bad. The Kanjis (and only the kanjis) look wrong (not antialiased, it even looks like it's not the same font).
To sum up:

  • alphabet and numbers: OK
  • hiragana and katakana: OK
  • kanjis: Bad rendering / wrong font

If you want to see the problem by yourself but not have any way to input Japanese, just paste this text:
abcd 1234 ひらがな カタカナ 漢字
You will see that the rendering of the 2 last characters is bad.

This is quite annoying. For example, try to copy paste the following sentence (from a news website):
水温35度「のぼせる」 夏休みのプール、開放中止相次ぐ

I think the problem can be solved by allowing the user to customize the fonts, or by selecting a font that has all characters in it (if a font that doesn't contain all characters is used, when a character not present in the font has to be rendered to OS will use another default font, so the characters won't match)

FYI, the new Skype client (also based on Electron if I'm not mistaken) also had this problem few months ago, but MS managed to fix it. As our organization is trying to leave Skype to use Wire we ope the issue can be solved quickly (PS: we can run tests if the need arises)

@ffflorian
Copy link
Contributor

On Windows 10 Chrome 74 the characters look like this:

Chrome

And look the same in Wire Desktop 3.9:
Wire

Is that what you mean?

@christophe-f8
Copy link
Author

christophe-f8 commented May 7, 2019 via email

@ffflorian
Copy link
Contributor

This was fixed in electron/electron#15486 and should already be applied in Wire for Desktop 3.12. Can you check if it was fixed for you @christophe-f8?

@ffflorian
Copy link
Contributor

Closing due to inactivity.

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

3 participants