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

Unicode Letters Can't Show in Telegram Desktop on Mac OS #6056

Closed
chenrylee opened this issue May 24, 2019 · 29 comments
Closed

Unicode Letters Can't Show in Telegram Desktop on Mac OS #6056

chenrylee opened this issue May 24, 2019 · 29 comments

Comments

@chenrylee
Copy link

Steps to reproduce

Install Telegram Desktop from App Store

Expected behaviour

Unicode letters, like 𝔖𝔶𝔩𝔳𝔞𝔫𝔞𝔰 𝔚𝔦𝔫𝔡𝔯𝔲𝔫𝔫𝔢𝔯, can't show,

Configuration

Operating system: Tested on Mac OS 10.12 and above

Version of Telegram Desktop: Test all versions so far

Used theme: Midnight

The letters show normally in Native Telegram for Mac.

@CssHammer
Copy link

Will this be fixed or what?

@Aokromes
Copy link
Collaborator

Aokromes commented Nov 7, 2019

can you try on 1.9.1 beta?

@CssHammer
Copy link

can you try on 1.9.1 beta?

Yes, still wasn`t fixed. I see rectangles instead of letters

@Aokromes Aokromes added the bug label Jan 26, 2020
@Aokromes
Copy link
Collaborator

Aokromes commented Mar 21, 2020

and on 1.9.21? :)

@chenrylee
Copy link
Author

and on 1.9.21? :)

I'm using the latest MAS version (1.9.13), some still can't show. And I found an interesting thing: When the letters are in name (incl. quote & reply), it can't show; while the letters are in message, it shows normally.

@doctor-frankenstein
Copy link

doctor-frankenstein commented Apr 28, 2020

Now i found in version 2.1 the special letters from UTF8 can display correctly at chat window, but still broken in profile, please check my screenshot

good at chat window

broken at profile

@gaplo917
Copy link

gaplo917 commented Jul 6, 2020

Still not able to show unicode in username in telegram desktop 2.1.

Screenshot 2020-07-06 at 1 06 02 PM

left: Telegram MacOS
right: Telegram Desktop
Screenshot 2020-07-06 at 1 04 59 PM

Sample text

𝑇𝑎𝑚𝑎𝑘𝑖

@Liam0205
Copy link

Any progress on this issue?

@Liam0205
Copy link

Telegram 2.1.13 on macOS reproduces this issue too.

@ilya-fedin
Copy link
Contributor

Any progress on this issue?

there can't be any progress since font rendering is completely on Qt side

@Aokromes
Copy link
Collaborator

@ilya-fedin
Copy link
Contributor

https://bugreports.qt.io/browse/QTBUG-59553

I dont' think that this bug is applicable for this issue, Qt has a problem with these glyphs with semibold style on any platform

@Liam0205
Copy link

Any progress on this issue?

there can't be any progress since font rendering is completely on Qt side

Well, I doubt it...

These chars could be shown correctly on the page of profile modification.

image
image

@Liam0205
Copy link

To me, it seems to be a font selection issue, rather than font rendering.

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Jul 21, 2020

To me, it seems to be a font selection issue, rather than font rendering.

Yes, Qt has problems with font selection (font fallback mechanism)

@Liam0205
Copy link

To me, it seems to be a font selection issue, rather than font rendering.

Yes, Qt has problems with font selection (font fallback mechanism)

Copy that.

Would you provide a workaround to bypass this problem?

@ilya-fedin
Copy link
Contributor

Would you provide a workaround to bypass this problem?

no, there are no workaround, unfortunately

@ilya-fedin
Copy link
Contributor

These chars could be shown correctly on the page of profile modification.

fallback is broken with the semibold style for some unknown reason

@Liam0205
Copy link

These chars could be shown correctly on the page of profile modification.

fallback is broken with the semibold style for some unknown reason

One of my friends reports that everything works fine on his macOS 10.15.5 (which is the same to mine). i.e., this issue is stably reproducible on my mac, but is stably irreproducible on his mac.
Why would this happen?

@ilya-fedin
Copy link
Contributor

Why would this happen?

It is better to ask Qt devs

@Liam0205
Copy link

I believe there might be something other than Qt causes this issue. It may be font configuration of macOS system preference.

I'll test this later this week, on a new installed macOS. If there will be any clues, I'll report them here.

@AndydeCleyre
Copy link
Contributor

I don't have access to macOS right now, but since SemiBold is mentioned here, I'll note that part of my workaround for fonts when building for Linux is replacing use of DemiBold with Bold, so you may want to try that:

$ sed -i 's/DemiBold/Bold/g' Telegram/lib_ui/ui/style/style_core_font.cpp

On my phone right now... That may not be proper syntax for the default sed on macOS.

@stale
Copy link

stale bot commented Oct 23, 2020

Hey there!

This issue will be automatically closed in 7 days if there would be no activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

@WuglyakBolgoink
Copy link

ping

@ilya-fedin
Copy link
Contributor

ping

Connection timed out

@0x1f415
Copy link

0x1f415 commented Jun 9, 2021

bumping as this continues to be a problem (on macOS).

interestingly the characters from the "Math Bold Script" set (eg 𝓪𝓼𝓭𝓯) display as boxes while fraktur (𝖆𝖘𝖉𝖋) text displays fine.

edit: oops, didn't see the "3rd party issue" tag.

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Jun 9, 2021

There's no reason to bump, only Qt devs can fix it

@csvnzzyd
Copy link

csvnzzyd commented Jul 27, 2021

all i see is square boxes.. did anybody find a resolution to this?

update:
I was able to fix if by running this command in terminal (using Debian Buster 10)

sudo apt-get install fonts-arphic-ukai fonts-arphic-uming fonts-ipafont-mincho fonts-ipafont-gothic fonts-unfonts-core

@stale
Copy link

stale bot commented Jan 24, 2022

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

@stale stale bot added the stale label Jan 24, 2022
@stale stale bot closed this as completed Feb 23, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests