On Mon, 21 Nov 2005 10:39:32 +0100
"Turner, David" <[EMAIL PROTECTED]> wrote:
>> About plugin, it is good idea (although I'm afraid
>> that FreeType is very very widely used on platforms
>> without dlopen etc), but it will be long way work.
>> It should be FreeType3, even if the binary compatibilit
Here's the patch again in requested format.
TK
--- freetype.h 2005-08-15 16:05:44.0 -0400
+++ freetype_1.h2005-11-21 15:49:16.0 -0500
@@ -1875,7 +1875,9 @@
const FT_Byte* file_base,
FT_Long file_size,
You can't use Qt3 ( didn't check Qt but afaik its the same ) with freetype2
from cvs because it uses internal freetype functions which are not exported
now.
But it's possible to provide a patch that only relies on public APIs and
structures to do the
same thing. That's what we've done for
Monday 21 November 2005 19:58 tarihinde, Ismail Donmez şunları yazmıştı:
> ( didn't check Qt but afaik its the same )
I meant Qt4.
/ismail
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-de
Monday 21 November 2005 17:05 tarihinde, Hans-Peter Jansen şunları yazmıştı:
> Am Montag, 21. November 2005 10:23 schrieb Ismail Donmez:
> > Monday 21 November 2005 11:08 tarihinde, Turner, David şunları
>
> yazmıştı:
> > > - fontconfig is buggy and uses FreeType internals when it shouldn't
> >
>
> The attached patch fixes a memory leak in bdfdrivr.c.
Applied, thanks.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
Am Montag, 21. November 2005 10:10 schrieb Werner LEMBERG:
> > While setting up 10.0 for an office environment, I noticed quite
> > bad font display due to kerning errors compared to earlier
> > versions.
> >
> > [...]
> >
> > That revealed a few problems, though. SUSE uses a patch to export a
> >
Am Montag, 21. November 2005 10:23 schrieb Ismail Donmez:
> Monday 21 November 2005 11:08 tarihinde, Turner, David şunları
yazmıştı:
> > - fontconfig is buggy and uses FreeType internals when it shouldn't
>
> This is now fixed in Fontconfig's fc-2_4_branch . But Qt still uses
> fontconfig internal
Am Montag, 21. November 2005 10:08 schrieb Turner, David:
> ello,
>
> the problem is different from what you think.
>
> - fontconfig is buggy and uses FreeType internals when it shouldn't
>
> - Suse's patch is a kludge to avoid fixing fontconfig
Well, I assumed this, too..
> - we're not transiti
> For systems that dont support dlopen() and only support static
> linking, the Amiga build can be used as example.
The forthcoming libtool version fixes bugs of libltdl on static
platforms. I would be glad if you could test whether libltdl (not
necessarily the libtool script itself) runs under A
> If you just want to test CVS freetype, you can use the attached
> _hack_ to make freetype export all symbols. Then all apps using
> freetype should compile.
>
> BTW, Should this hack be included in CVS temporary? Current CVS
> sort of discourages people from testing.
Good heavens, no! Such c
> While setting up 10.0 for an office environment, I noticed quite bad
> font display due to kerning errors compared to earlier versions.
>
> [...]
>
> That revealed a few problems, though. SUSE uses a patch to export a
> bunch of methods from the ftstream module,
Uh, oh, we are in the process of
On Mon, 21 Nov 2005, Ismail Donmez wrote:
> Monday 21 November 2005 11:08 tarihinde, Turner, David şunları yazmıştı:
> > - fontconfig is buggy and uses FreeType internals when it shouldn't
>
> This is now fixed in Fontconfig's fc-2_4_branch . But Qt still
> uses fontconfig internals :(
That's bei
> Turner, how do you think of? We should start from
> strict and adding capability for exceptional cases?
> Or, unaligned memory access is different issue and
> should be validated strictly from initial revision?
>
It depends on what your client wants. Some processing engines
are capable of dealin
Le lundi 21 novembre 2005 à 10:08 +0100, Turner, David a écrit :
> ello,
>
> the problem is different from what you think.
>
> - fontconfig is buggy and uses FreeType internals when it shouldn't
>
> - Suse's patch is a kludge to avoid fixing fontconfig
>
> - we're not transitioning from FT_EXPO
Hello mpsuzuki,
as Werner said, there is no need to apologize. The OpenType and
GX specifications are extremely complex (and underspecified),
and it's very difficult to get this code right.
I'll restate my point that I believe that the validation and
processing code should be part of the same lib
Monday 21 November 2005 11:08 tarihinde, Turner, David şunları yazmıştı:
> - fontconfig is buggy and uses FreeType internals when it shouldn't
This is now fixed in Fontconfig's fc-2_4_branch . But Qt still uses fontconfig
internals :(
Regards,
ismail
__
ello,
the problem is different from what you think.
- fontconfig is buggy and uses FreeType internals when it shouldn't
- Suse's patch is a kludge to avoid fixing fontconfig
- we're not transitioning from FT_EXPORT to FT_BASE. FT_EXPORT is
the only macro used to export public API names. FT_BA
On Mon, Nov 21, 2005 at 01:06:22AM +0100, Hans-Peter Jansen wrote:
> (FT_Stream_OpenGzip and FT_Stream_OpenLZW still used FT_EXPORT).
They should be FT_EXPORT'ed as they are not used inside freetype.
I don't know how to use them though.
> That leaves me with a couple of questions:
> - Should I pre
> > In memory optimized `tt_sbit_decoder_load_image', when
> > index_format is 2 or 5, image_offset is added to image_start
> > twice.
> >
> > This bug is trivial. But as I don't have a font to test, I send
> > this patch to the list for review, in case I misunderstood the
> > code.
>
> I've commi
20 matches
Mail list logo
