Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Rendering text does not work correctly
#1
This is how the standard GDI output should work:

[Image: ml3eTTn.png]

Instead, Cent Browser ALWAYS renders like this. No matter what I do to the disable DirectWrite settings, etc. it looks exactly like a DirectWrite render.

[Image: XyZNfab.png]

It's possible to truly test this by going to https://fontgammatest.netlify.com/ .

[Image: 68747470733a2f2f692e696d6775722e636f6d2f...342e706e67]
(be sure to view this image at pixel-perfect size to properly view the text samples)

And CentBrowser is unfortunately never any different from DirectWrite, which is no different from the bad ultramodern browsers.
Reply
#2
Bump. This is a deal breaker.

fontgammatest.netlify.com

Although classic GDI passes the test, Cent Browser never does, it appears to not use GDI correctly.
Reply
#3
Sorry but I see no much difference among these samples.
We change Gamma value of Skia if DirectWrite is disabled.
And the value was the same as Firefox.
Users that have disabled DirectWrite mostly use MacType to increase font render.
Reply
#4
The difference is still evident, so Cent Browser does not use GDI rendering, which is a major issue.
Reply
#5
......
Reply
#6
(03-24-2020, 07:00 PM)45afc4td Wrote: The difference is still evident, so Cent Browser does not use GDI rendering, which is a major issue.
You can try using MacType, and check the result.
Reply
#7
Uh, no. That doesn't work. I want actual GDI rendering as it is.
Reply
#8
Why are the developers so ignorant of text rendering?
Reply
#9
(03-31-2020, 07:03 PM)45afc4td Wrote: Why are the developers so ignorant of text rendering?
I think the rendering effect of disabling DirectWrite is acceptable.
Reply
#10
Acceptable to users, you mean?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)