lmaook / mactype

Automatically exported from code.google.com/p/mactype
0 stars 0 forks source link

Text rendering working again in Chrome 30+? #79

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I stumbled upon a Chinese blog in which the author claims that the latest 
Chrome v30 beta, in addition to a video driver update, has fixed gdi++ font 
rendering.

http://wingtilldie.blogspot.jp/2013/08/GDIPP-render-chrome.html

I wonder if anyone can confirm this for mactype?

Original issue reported on code.google.com by jmbat...@gmail.com on 6 Aug 2013 at 2:16

GoogleCodeExporter commented 8 years ago
As you mentioned, the author uses another version (GDI++ 氦版), which is 
different from mactype. 

Original comment by albertle...@gmail.com on 15 Aug 2013 at 10:00

GoogleCodeExporter commented 8 years ago
I see.

But do not gdi++ and Mactype not utilise similar (the same) code?
I gather that gdipp is a rewrite of gdi++, but thought Mactype reuses elements 
of gdi++.

Original comment by jmbat...@gmail.com on 19 Aug 2013 at 7:35

GoogleCodeExporter commented 8 years ago
Sure mactype reused lots of code from gdi++, but mactype solved alot of bugs 
exist in gdi++ including the "Chrome rendering bug".

Chrome is always render-able with mactype no matter what version of chrome you 
are using.

Original comment by flyingsn...@gmail.com on 30 Aug 2013 at 3:57

GoogleCodeExporter commented 8 years ago
>Chrome is always render-able with mactype no matter what version of chrome you 
are using.

May I ask what you mean by 'render-able'?

For me, mactype smooths fonts up to Chrome version 17.0.963.83, but after this 
version the smoothing is no longer applied.  Please compare the two screenshots 
below.

Thank you!  

Original comment by jmbat...@gmail.com on 13 Sep 2013 at 1:54

Attachments: