Bug#385798: openoffice.org: font hinting still does not work with the current version ob libfreetype
Hello,
Rene Engelhard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Rene Engelhard wrote:
>> Ah, it's in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378619
>> where you didn't refer to..
You are referring to
http://www.openoffice.org/nonav/issues/showattachment.cgi/36573/vcl-freetype-2.2.x.diff,
don't you?
>
> - --- snip ---
> #
>
> OpenOffice
> All current versions of OpenOffice.org include internal headers; this
> will be fixed either in 2.0.3 or 2.0.4. (The fix is applied to the CVS,
> but still waiting for approval for the 2.0.3 branch).
>
> Until then, you can use this patch.
> - --- snip ---
>
> reading this, can you try 2.0.4rc1 (2.0.4rc2 coming soon) in sid and try
> whether it works there?
I just checked it myself, the patch is included into 2.0.4rc1, slightly
different, as in 2.0.4rc1 fist the unsigned's are defined and from it the
signed's, but that shouldn't matter (if I'm not entirely mistaken at this
late hour).
typedef const unsigned char* CPU8;
inline sal_uInt16 NEXT_U16( CPU8& p ) { p+=2; return (p[-2]<<8)|p[-1]; }
inline sal_Int16 NEXT_S16( CPU8& p ) { return (sal_Int16)NEXT_U16(p); }
inline sal_uInt32 NEXT_U32( CPU8& p ) { p+=4; return (p[-4]<<24)|(p[-3]<<16)|
(p[-2]<<8)|p[-1]; }
//inline sal_Int32 NEXT_S32( U8*& p ) { return (sal_Int32)NEXT_U32(p); }
NEXT_S32() is really not used in gcach_ftyp.cxx.
The problem is that the bytecode interpretation doesn't work, I just asked
several questions on the freetype-list:
http://lists.nongnu.org/archive/html/freetype/2006-09/msg00050.html
Sasha, is this the same problem you have?
Cheers,
Bernd
Reply to: