Closed chenrylee closed 2 years ago
Will this be fixed or what?
can you try on 1.9.1 beta?
can you try on 1.9.1 beta?
Yes, still wasn`t fixed. I see rectangles instead of letters
and on 1.9.21? :)
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.
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
Still not able to show unicode in username in telegram desktop 2.1.
left: Telegram MacOS right: Telegram Desktop
Sample text
ππππππ
Any progress on this issue?
Telegram 2.1.13 on macOS reproduces this issue too.
Any progress on this issue?
there can't be any progress since font rendering is completely on Qt side
I dont' think that this bug is applicable for this issue, Qt has a problem with these glyphs with semibold style on any platform
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.
To me, it seems to be a font selection issue, rather than font rendering.
To me, it seems to be a font selection issue, rather than font rendering.
Yes, Qt has problems with font selection (font fallback mechanism)
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?
Would you provide a workaround to bypass this problem?
no, there are no workaround, unfortunately
These chars could be shown correctly on the page of profile modification.
fallback is broken with the semibold style for some unknown reason
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?
Why would this happen?
It is better to ask Qt devs
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.
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.
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!
ping
ping
Connection timed out
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.
There's no reason to bump, only Qt devs can fix it
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
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!