Font rendering broken in Google Chrome developer build (18)

[GoogleCodeExporter]

Which program triggers the problem? Specify the filename if possible.

What steps will reproduce the problem?
1. Open Chrome
2. View any web page

What is the expected output? What do you see instead?
Expect to see fonts render as normal.  When updated to dev build 18, all font 
rendering is broken and unreadable.

What version of gdipp (including renderer)? On which operating system?
0.91 x64 on Windows7 x64

Please provide any additional information below. Screenshots always help.

Original issue reported on code.google.com by shawngma...@gmail.com on 11 Jan 2012 at 9:42

Attachments:

• gdipp_chrome_render.gif

[GoogleCodeExporter]

Disabling "GPU Accelerated Drawing" does not work for me. 
In fact, I think I've tried every possible 'disable' related with GPU, WegGL 
and/or accelerated-something.

I've also tried using http://drwatson.nobody.jp/gdi++/ (I don't know why, just 
hoping it would help...), but got no results.

Is there any workaround?

Thanks

Original comment by horaciojk on 8 Jun 2012 at 5:40

[GoogleCodeExporter]

(about the workaround)
OK. I didn't know ezgdi was running on my machine...
Once I've uninstalled it, Chrome problems were solved.

Original comment by horaciojk on 8 Jun 2012 at 6:07

[GoogleCodeExporter]

Workaround worked for me. 
Edit C:\Program Files(x86)\gdipp_setting.xml and add a line 

<process>chrome\.exe</process> 

in the <exclude> section to disable gdipp.

Then reboot or
Run services.msc, find the 32 and 64 bit instances of gdipp and restart each 
one.

Original comment by VEZam...@gmail.com on 19 Jun 2012 at 3:38

[GoogleCodeExporter]

PLEASE REMOVE ME FROM THE EMAIL LIST I DONT GIVE A FUCK ABOUT GDIPP

Original comment by JSW.jame...@gmail.com on 21 Jun 2012 at 6:37

[GoogleCodeExporter]

Remove yourself, dammit!

Original comment by fitoschido on 21 Jun 2012 at 11:46

[GoogleCodeExporter]

Font rendering in Chrome is horrible. Simply compare any page in Chrome to the 
same in Firefox or IE9 and the differences are plain as day. Jagged rough edges 
that do not appear anti aliased/hinted vs those that are smooth and crisp. The 
differences are especially noticeable on medium sized display/headline text. 
Smoothing hacks no longer work, although they shouldn't have ever been 
necessary in the first place. This doesn't seem to be something the Chrome dev 
team wants to address since it hasn't been dealt with at all during the entire 
lifetime of the product, but it is a major issue.

Original comment by fat...@gmail.com on 27 Jun 2012 at 3:29

[GoogleCodeExporter]

Is anything happening with this issue? Font rendering is so bad in Chrome that 
I loathe  to think about people visiting my sites with this browser and seeing 
what is supposed to be impeccable typography marred by nasty jaggy type. When 
can we expect a fix to bring this browser up to par visually with Firefox, IE9 
and Safari?

Original comment by fat...@gmail.com on 15 Jul 2012 at 4:36

[GoogleCodeExporter]

In re: comment 57: I'm not sure what you think the issue is here. The only 
people who would be experiencing bad type on your site are the same people 
experiencing bad type on ALL the websites they go to on Chrome to a degree that 
it is unreadable and therefore unusable. Chrome is simply not used at all if 
GDIPP is still enabled with it, so I'm not clear why you would have any fear 
with your site particularly. The only people running GDIPP are people with the 
brains to install it anyway, not general public.

This thread is dead. GDIPP can't hold a finger to Mactype and Chrome can be 
disabled in GDIPP independently if you really have some attachment to it. Issue 
resolved. If you have some other issue with text rendering on Chrome not 
related to GDIPP, then start a new thread.

Original comment by iisilsp...@gmail.com on 15 Jul 2012 at 5:32

[GoogleCodeExporter]

OK, let me put it another way. Font rendering in Chrome is terrible full stop. 
When is this going to be fixed?

Original comment by fat...@gmail.com on 15 Jul 2012 at 5:46

[GoogleCodeExporter]

And I quote myself,

"If you have some other issue with text rendering on Chrome not related to 
GDIPP, then start a new thread."

Original comment by iisilsp...@gmail.com on 15 Jul 2012 at 5:48

[GoogleCodeExporter]

comment 58: "GDIPP can't hold a finger to Mactype..."

I do not agree.  From what I can gather Mactype is based on the older gdi++, 
whereas gdipp is rewritten from scratch and therefore a more modern 
implementation.

It's obviously unfortunate that version of Chrome after 17.0.963.83 cause 
rendering issues, but I am still hopeful that these will be addressed in a 
future gdipp release.

Original comment by jmbat...@gmail.com on 17 Jul 2012 at 11:33

[GoogleCodeExporter]

Comment 53 worked for me, thanks a lot. :)

Original comment by electrifyings on 31 Jul 2012 at 5:14

[GoogleCodeExporter]

Chrome renders my website's font in an awful way , FireFox similarly , IE is 
the best.

Funny thing using Google Fonts which Google's browser renders poorly .. what a 
joke.

Original comment by globalso...@gmail.com on 21 Sep 2012 at 2:38

[GoogleCodeExporter]

I too faced the similar issue with Chrome the menu font are displayed in a bad 
way in Chrome browser. I tried to update the Chrome to version 23.0.1271.1 and 
the fonts are good. They are as is, my guess its not using the gdipp font 
rendering and rest of the windows applications are using it!

Original comment by samishch...@gmail.com on 26 Sep 2012 at 6:11

[GoogleCodeExporter]

Comment 53 worked for me TOO  yeah :D thanks! 

Original comment by scan300...@gmail.com on 26 Sep 2012 at 6:14

[GoogleCodeExporter]

My type/font are raggedy and screen background is not solid but dot screen. 
Please HELP. My eyesight is not that good.
Minerva Coyne@gmail.com

Original comment by minervac...@gmail.com on 18 Nov 2012 at 2:58

[GoogleCodeExporter]

Mine is completely unreadable.

Original comment by vilio...@gmail.com on 7 Dec 2012 at 7:05

[GoogleCodeExporter]

Comment #53 is a functioning workaround, so do that if you're still having 
problems.

To edit an .xml file, right click it and Open With. . . in Notepad

When you've added the new line of code(see #53), Save As. . . it to the desktop 
without renaming it

Once saved, drag it into the original folder containing the .xml file

Overwrite the original with the new edit, and you're good to go.

The reason for this is .xml files are typically not supposed to be edited, so 
you can't just save it in the Notepad.

Original comment by ThatWann...@gmail.com on 21 Feb 2013 at 7:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I am getting this problem with version 30.0.1599.101 m on Windows 7.  All 
suggestions have been tried, including reset to original default setting.  The 
pages with the weird characters also include properly rendered text.  When cut 
and pasted into notepad weird text displays correctly. 

Original comment by jkoern...@gmail.com on 17 Oct 2013 at 4:33

[GoogleCodeExporter]

Windows Registry editing fixed the font thickness issue for me completely, 
we can tune the font thickness/darkness by calibrating  FONTSMOOTHINGGAMMA  
value to between 150 and 190 hexadecimal( 336 to 400 decimal )

  -   START  ->  RUN  ->  REGEDIT
  -   search for  FONTSMOOTHINGGAMMA   by  keying  "Ctrl F"
       ( will automatically take us to  CurrentUser\ControlPanel\Desktop  path)
  -   double-click mouse on  FONTSMOOTHINGGAMMA   enter any 
      thing between 150 and 190 hexadecimal.
        (the Lower the value, the thicker the fonts.)
  -   close the REGEDIT tool
  -   LOGOFF and then LOGON

Now all the fonts are very thick & very dark in Chrome Browser.

But we must make sure that ClearType smoothing is enabled in Windows
( controlPanel  ->  personalization  ->  appearance
          ->   Effects  ->  ClearType smooth check (ticked box) )

                         OR  alternately in RegEdit ...

             FONTSMOOTHING=2
             FONTSMOOTHINGTYPE=2
             FONTSMOOTHINGORIENTATION=1  for LCD-screen,  0 for CRT-screen

Original comment by yv.rao...@gmail.com on 26 Oct 2014 at 8:29