Nevertheless the fonts should look fine with default settings. But it
may look better with all features enabled.
Fonts look fine, yes, but don't expect them to look better by adding bytecode which is IGNORED.
Sigh, mf
--- mf mf@mufunyo.net wrote:
Nevertheless the fonts should look fine with
default settings. But it may look better with all features enabled.
Fonts look fine, yes, but don't expect them to look better by adding bytecode which is IGNORED.
Sigh, mf _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Marlett is small enough (only 30 or so glyphs) that I could still throw on some bytecode hints. I had started work on doing just that, but I had to halt work on it while I do my homework for this course cycle.
I sent Hartmut an SBITed version that contains cleaned up bitmaps for sizes 8 through 16pt, but he made a test case that tests at much higher sizes, where the bitmaps obviously wont patch the missing/erroneous behavior.
It is my understanding that Freetype "Kludges" its way around the "patented Bytecode" using a (broken) interpolation mechanism. This gives a "half ass" fix for the problem, but doesnt give proper subpixel relocation. This means that the hints I add will likely be misinterpereted by Freetype, just like they were with Greenville, but hopefully that wont be such a big problem, since it will be for 'large' sizes.
We'll find out soon enough.
____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL