Truth Behind the ClearType/OpenSUSE FUD 123
Posted
by
kdawson
from the making-it-clear dept.
from the making-it-clear dept.
Kennon writes "Steven J. Vaughan-Nichols over at Linux Watch clears up the FUD around Tuesday's Slashdot discussion concerning OpenSUSE, ClearType, and patent deals with Microsoft."
Not everything is a conspiracy (Score:3, Informative)
So it would seem that the disabling of FreeType is more coincident than anything else. It's possible for parallel processes to affect the same thing but have no overt connection.
Re:This hurts my head (Score:5, Informative)
Re:This hurts my head (Score:2, Informative)
Re:This hurts my head (Score:5, Informative)
There seems to be a confusion of terminology in the above, but I admit I may be misreading it.
Anti-aliasing is not the same thing as sub-pixel rendering, which is orthogonal to anti-aliasing and can be (and almost always is) combined with it.
Anti-aliasing is merely the use of different shades to adjust the sharpness of object boundaries, where the shade is based upon the amount of a pixel the objects covering that pixel would intersect. While this sounds like something that would be describable by the term "sub-pixel rendering" if, for a moment, you assume you would divide the pixel into smaller virtual pixels to calculate the end result, that's not what sub-pixel rendering refers to. The term "sub-pixel" is not being used to describe these smaller "virtual pixels".
In an LCD a pixel is made up of three "sub-pixels": real, discrete, lighting elements that together illuminate one complete pixel. The sub-pixels are the three primary colours and are almost always mounted side by side as three thin strips. Sub-pixel rendering is the technique of using the separate red, green, and blue sub-pixels of an LCD "pixel" in isolation to improve the sharpness of object boundaries. When used, the screen effectively has an increased horizonal resolution of 3x the regular resolution, so a 1400x1050 screen effectively becomes 4200x1050.
It is usually, if not always, used in conjunction with regular anti-aliasing (though technically it doesn't need to be.)
Microsoft's patents, as I understand it, cover the latter, and in particular focus on preventing "colour fringing" that is otherwise a major downside of using sub-pixel rendering.
Re:ClearType draws from Apple II, says developer (Score:3, Informative)
http://www.grc.com/ctwho.htm [grc.com]
Re:Changed Before the Microvell Deal (Score:5, Informative)
From my standpoint, the interesting issue that remains is what I mentioned in the little comment at the end of my submission for the previous story: ok, assuming there are MS patents on this technology, isn't Novell licensed to use them now (even if it "isn't a patent license", but it just acts like one)? Apparently the Microsoft-Novell deal doesn't help openSUSE out much with regard to MS patents. Is the same true for SUSE?
Re:Software patents at devices. (Score:1, Informative)
Really, I recommend if you are going to bash anything, whether patents, copyrights, or some large corporation of your choice that you do a little research into what it is you are saying, before spewing total non-sense and spreading Fear, Uncertainty, and Doubt of your own.
Re:Microsoft didn't invent this idea. (Score:1, Informative)
Microsoft's ClearType seems to combine the old Truetype bytecode hinting instructions with sub-pixel detail, filtering the results to remove color fringing. IMHO this results in the most readable text I've ever seen on a computer monitor.
YMMV.
Re:Changed Before the Microvell Deal (Score:3, Informative)
Re:OS X's subpixel rendering? Adobe's "CoolType"? (Score:2, Informative)
c.f. http://www.grc.com/ctwho.htm [grc.com]
Re:This hurts my head (Score:2, Informative)
Re:OS X's subpixel rendering? Adobe's "CoolType"? (Score:4, Informative)