Frederic Crozat wrote:
I *DO* use cooker. And it is not fixed - try to go to that (any) site in the bug report - http://underground.cz ; the coding is fixed (Mozilla will use iso-8859-2 correctly), but if you manually switch to UTF-8, still the same - mostly empty lines.On Wed, 19 Feb 2003 19:22:34 +0100, Michal Bukovjan wrote:Hi Frederic/Cooker, could you please comment on this bug? http://bugzilla.mozilla.org/show_bug.cgi?id=182650You don't use cooker, do you ?
This bugs me from time to time on arbitary sites than happen to have an "unsupported" char in the middle of a line of text.
I only replace Cooker XFree86 drivers with GATOS ones, as I need video recording and TV capabilities, but I don't think it matters.
Now that would be pity - I used the hack for some time, it is very stable and current Cooker rendering just looks mediocre when compared :-(.Because I fixed this a LOOONG time ago :)Also, do you plan to use freetype2-2.1.4 once it comes out (currently at rc1) or at least integrate the once discussed hack into 2.1.3, in spite of feature freeze? The rendering difference is *really* worth it.
I won't integrate hacks from Freetype CVS in our Freetype (except if some fonts don't load with our Freetype).. I don't think Freetype 2.1.4 will be in Mdk 9.1, except if it is released this week..
But it's your decision - I hope someone will release an updated rpm then, so that font rendering is pleasant again.
Michal
