search

taikodaigo / gdipp

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

Chrome's text rendering is... fucked. #198

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Which program triggers the problem? Specify the filename if possible.
Google Chrome 15

What steps will reproduce the problem?
1. Open any website

What is the expected output? What do you see instead?
I expected to see a website with text, instead I got something unreadable (see 
attachment)

What version of gdipp (including renderer)? On which operating system?
gdipp 0.9.1 x64 on Windows 7 Ultimate x64

Please provide any additional information below. Screenshots always help.

Original issue reported on code.google.com by samusa...@bubbelsearch.de on 8 Nov 2011 at 7:48

Attachments:

GoogleCodeExporter commented 8 years ago 
http://code.google.com/p/gdipp/issues/detail?id=182

Original comment by jmbat...@gmail.com on 9 Nov 2011 at 12:30

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Update to Chrome 18.0.1025.142 on Windows 7 Home Basic x86, gdipp 0.9.1 x86 
experiencing the same problems.

Original comment by xru...@gmail.com on 29 Mar 2012 at 2:43

GoogleCodeExporter commented 8 years ago 
Chrome is using Skia text rendering which causes the various issues. I suspect 
the only option here is to disable it in gdipp.

Original comment by frcg...@gmail.com on 9 May 2012 at 12:36

GoogleCodeExporter commented 8 years ago 
is this going to be fixed? I can't read shit when I use Chrome now.

Original comment by adam.us...@gmail.com on 17 May 2012 at 9:36

GoogleCodeExporter commented 8 years ago 
Still happening with chrome 19.0.1084.52 and gdipp 0.9.1 x86

Original comment by sami.sam...@gmail.com on 14 Jun 2012 at 4:59

GoogleCodeExporter commented 8 years ago 
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 rendering when using chrome.

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

This was done on Win7 Pro x64 and gdipp 0.9.1 x64

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

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
@VEZam

That's not a workaround you idiot. That's the same thing as disabling gdipp and 
calling it a "workaround".

Not that I use Chrome or ever would install spyware, but I just wanted to point 
that out.

Original comment by Dissolut...@gmail.com on 20 Jun 2012 at 2:17

GoogleCodeExporter commented 8 years ago 
What eloquence! Your unbiased, respectful, and collected nature drives me to 
want to hear more.

Anyway, I would consider that to be a workaround. It doesn't necessarily solve 
the issue, but it is a way to work around parts it. It at least solves the 
problem of illegible shadowed text.

Original comment by fernoz...@gmail.com on 24 Jun 2012 at 12:26