Newer versions of Visual Studio have trouble with IE 8.
Poor font rendering in Windows 8 (blurry text)
Apparently there is a huge problem with **** font rendering in Windows 8. Text appears very blurry. Programs affected by the new rendering are: Internet Explorer 10, the modern interface (start screen), Office 2013 and other 3rd party applications that rely on this rendering technology. There is no way to fix this problem, unless Microsoft recognizes it.
I 've gathered links bellow that refer to the same problem to highlight its importance and display the number of users that are affected:
Microsoft MSDN/TECHNET
External forums:
http://www.neowin.net/forum/topic/1120890-internet-explorer-10-fonts-fuzzy-in-windows-8/
http://www.eightforums.com/browsers-mail/5432-blurry-text-ie10-desktop.html
http://www.techsupportforum.com/forums/f56/blurry-website-fonts-in-ie10-675564.html
http://www.techplex.net/postst78315_Text-in-Internet-Explorer-10-and-Metro-UI-is-blurry.aspx
and there are lots of more...
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
518 answers
Sort by: Oldest
-
Anonymous
2013-12-12T17:49:21+00:00 -
Anonymous
2013-12-12T17:56:53+00:00 Newer versions of Visual Studio have trouble with IE 8.
Isn't (a developer's) life funny...
PS: no offense, just grinning how many version-interop-permutation-possibilities sum up and make our jobs harder, but keep the brain up and running while looking for solutions ;-)
-
Anonymous
2013-12-17T16:55:12+00:00 Also having font rendering problem on Windows 8.1, I found MacType as a Google Code Project : https://code.google.com/p/mactype/
And I'm really satisfied of the rendering after installation.
I don't have any screenshot, and I know it's not a long term solution but I really recommend this little software.
-
Anonymous
2013-12-30T02:11:44+00:00 That's not a solution but a tedious workaround to a problem that exists solely because MS switched Windows to grey-scale anti-aliasing. Much easier to just use nonwindows progs.
Much confusion in this thread...
The problem does *not* arise from switching to grayscale anti-aliasing, but from switching to hardware rendering (directwrite) and from not giving us an option to disable it.
In fact, I love grayscale font smoothing, always liked it.
And I don't remember people complaing about blurry fonts in the olden times when there was just the choice between a) "unsmoothed" font rendering and b) the socalled "standard font smoothing" (=grayscale).
We had these options (if I recall correctly) since Windows 95 (with plus pack), and of course in Windows 2000 and XP. And fortunately, this traditional way of font smoothing can still be used instead of headache-inducing Cleartype until today in Windows 7 and 8.
Nothing beats crispness in grayscale smoothing in all kinds of Windows (as compared to Linux which only comes close but not enough for me to enjoy reading long texts - all fontconfig settings tried, nothing helps to get the same degree of sharpness). Standard font smoothing (grayscale) is still the best for my eyes, while Cleartype is completely useless (for me) giving me hurting eyes and headaches.
I understand that some (many?) people in this very long thread miss RGB font rendering (coloured Cleartype subpixel rendering). That's okay, if you like it that way.
Nevertheless, I still claim that this is not the root of the Windows 8 font rendering issue.
As I said, it is the switch to hardware rendering and the lack of an option to disable it or to even use coloured rendering.
If there were such an option, people would be free to use any of those 3 (or 4) options:
- unsmoothed
- grayscale
- Cleartype
- directwrite
What is so hard to offer these various options?
-egman-
-
Anonymous
2013-12-30T10:14:37+00:00 That's not a solution but a tedious workaround to a problem that exists solely because MS switched Windows to grey-scale anti-aliasing. Much easier to just use nonwindows progs.
Much confusion in this thread...
The problem does *not* arise from switching to grayscale anti-aliasing, but from switching to hardware rendering (directwrite) and from not giving us an option to disable it.
In fact, I love grayscale font smoothing, always liked it.
And I don't remember people complaing about blurry fonts in the olden times when there was just the choice between a) "unsmoothed" font rendering and b) the socalled "standard font smoothing" (=grayscale).
We had these options (if I recall correctly) since Windows 95 (with plus pack), and of course in Windows 2000 and XP. And fortunately, this traditional way of font smoothing can still be used instead of headache-inducing Cleartype until today in Windows 7 and 8.
Nothing beats crispness in grayscale smoothing in all kinds of Windows (as compared to Linux which only comes close but not enough for me to enjoy reading long texts - all fontconfig settings tried, nothing helps to get the same degree of sharpness). Standard font smoothing (grayscale) is still the best for my eyes, while Cleartype is completely useless (for me) giving me hurting eyes and headaches.
I understand that some (many?) people in this very long thread miss RGB font rendering (coloured Cleartype subpixel rendering). That's okay, if you like it that way.
Nevertheless, I still claim that this is not the root of the Windows 8 font rendering issue.
As I said, it is the switch to hardware rendering and the lack of an option to disable it or to even use coloured rendering.
If there were such an option, people would be free to use any of those 3 (or 4) options:
- unsmoothed
- grayscale
- Cleartype
- directwrite
What is so hard to offer these various options?
-egman-
No, you're wrong, the problem DOES arise from switching to grayscale antialiasing and not due to hardware rendering.. It's the coloured antialiasing that made the font (in IE for instance) much more readable.. Hardware rendering already been part of font rendering in windows for some time, but only with Windows 8 they switched from 'coloured' antialiasing to grayscale..
The simple point is: Font rendering (for IE-based rendering) is fubar in Windows 8 compared to Windows 7 and earlier, no matter what the real reason is.. The problem has already been acknowledged by the developmentteam with a message that it will not be changed (at least at the time of the answer, but then again, they are comming back on a lot of poor decissions made in Windows 8)..