-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Chromium unicode fallback mechanism broken for Win7 #16
Comments
that's because chromium uses the system font, firefox uses a built-in one |
That doesn't sound right - are you telling me that Chromium uses only ONE singular font from the system? Which one? There are a few fonts that are used in various parts of the system. Doesn't sound right - there is no singular font that is capable of taking the entirety of Unicode. So that would be a serious design flaw if that was the case. Also, Firefox is capable of using system fonts with a font fallback. I noticed that when I installed a slew if huge fonts - whereas Firefox showed invalid characters for Egyptian hieroglyphs, after installing those system fonts, Egyptian hieroglyphs would now show up (in a very pixelated way, but still). |
Please report this issue to Google |
And if it is a Win7-specific problem? |
Try supermium and see if the problems you encountered still occur. If supermium does not have this problem, then I will reopen this issue. |
Nope, I can for example use and see more symbols (when used as a file name) in Win7... than Win10. I do have a modified Segoe UI Symbol and Segoe UI Emoji, among fallback and many big fonts. :) What's Twitter?
And have you tested the very site I made printscreens of? You should've checked... ;) |
If I put that link to you it is so that you could see first hand a real test of the unicode characters without any kind of coding. ok? Firefox already have embedded fonts meanwhile Chromium replace Noto sans with another similar of your system |
No. |
Just by the way, this is still an issue. Maybe the Supermium author could work on this, now that we have GDI font rendering back? https://www.amp-what.com/unicode/search/rock https://www.fontspace.com/unicode/char/1F66E-rightwards-rocket I have both of these installed,... ...yet I do not see the symbols. (The Install button is disabled because those are already installed...) |
@JaegerFox @gz83 @Templayer Seems this isn't a Thorium specific problem, and y'all are also running modified Windows OSes. I cant devote time to this because there is already a backlog of work that needs to be done in both Thorium and Mercury. Sorry. If Supermium or upstream makes a fix for this, lemme know and I'll add it to the codebase. |
Yup, I am (now) well aware that this Issue should be pushed upstream to Supermium, as was mentioned in the Issue thread by other people. For now, I have removed the Adblock Plus filter for web fonts, because that didn't affect this Issue in any way, shape or form (the result is the same no matter if webfonts are enabled or disabled). |
@Templayer Does it work OK with latest M122 and using the noto font pack? |
I had the Noto fonts installed when I made this issue way back. Which was my point - the browser wasn't falling back to system fonts (like Noto) properly. That was my entire point. Yet people were telling me that "Firefox has build in emojis and fonts". Firefox loads Noto fonts fine. It can even show things like hieroglyphs through Noto. Thorium: Firefox (without using build-in stuff): Firefox uses Noto Color Emoji from the system correctly:
Thorium shows that same font-family, but is unable to get the font from the operating system: |
I'm starting to suspect that the only thing different is the way Firefox and Supermium enumerate system fonts. I have weirdly INTERNALLY named font families for several fonts (containing nonstandard characters). Maybe that is why the enumeration fails and it never actually gets to Noto in the first place? Could somebody check if Thorium/Supermium still gets all system fonts if the following fonts are installed in the system? The "C.A.Gatingas" font was renamed internally by removing the dots, as the font was crashing several kinds of software, but I am going to pack it too (it's the entire reason why I thought of this problem in the first place). "Fanfarron" still has a diacritical symbol internally, while "a-e-i-o-u" has "_". "Metalona" seems to have "*". "hit-me-punk.01" has "," and "!" internally. Nonstandardly internally named fonts.zip I tried to specify "INTERNALLY" several times, as I am referring to the internal font name, not the filename or anything else. |
@Templayer @JaegerFox This has been fixed in this commit > fdeb628#diff-02a23746537481b5b5e961197ae121bcdb6227527212aca8cc096f0433aa00f3 Next builds should have it fixed. Same issue as #83 |
So I wasn't going crazy the entire time and it really is/was an issue. Great! I was worried there for a sec, but the small pink elephant in the corner told me everything was going to be OK. YAY! |
@Templayer Yeah, it was an issue even in M109, which is strange considering this had official Win7 support. |
I'm still in 122 for Win7. When will the Thorium Legacy with this fix arrive so I can test if this was fixed or not? |
@Templayer Building new releases for XP and 7 right now! This release is still based on M122, but has alot of fixes from win32ss, myself, and upstream, as well as backported features from regular M124 Thorium. Stay tuned! |
Still occurs in the new version. Even with most of my extensions disabled (I had to reinstall them all).
I still wonder about the font enumeration. |
System Details
Problem
It seems like Chromium and Chromium-based browsers have problems with Unicode fallback mechanisms under Win7. See screenshots for more details. I just noticed that some pages have invalid glyphs for buttons, etc. This isn't a Thorium issue per se, but a Chromium issue with Win7 (at least it appears to be at a first glance).
How to test: Look at glyphs on https://www.amp-what.com/unicode/search/cross while having big Unicode fonts installed.
Screenshots
Firefox for comparison (all glyphs accounted for):
Thorium:
Chromium (old version):
Fonts installed in the system:
Font List.docx
With fonts embedded into the docx file: UNFORTUNATELY, I CANNOT UPLOAD a 7z file due to retarded github limitations (not a supported file type!) and I had to store it in a zip file... goddamit!
Font List.zip
Both Noto Sans Symbols2 and Symbola have the missing glyph. Why is Chromium/Thorium not able to check these under Win7?
The text was updated successfully, but these errors were encountered: