> > -Antialiasing (ON), Hinting(ON)
>
> FT_LOAD_TARGET
Oops, should be FT_LOAD_TARGET_NORMAL.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
> I will appreciate, if someone can give pointers to Load
> (FT_LOAD_XXX) and Render(FT_RENDER_XXX) flags to be used in
> ver. 2.1.10.
>
> Specifically for following scenarios:
>
> -Antialiasing (ON), Hinting(ON)
FT_LOAD_TARGET
> -Antialiasing (ON), Hinting(OFF)
FT_LOAD_TARGET_NORMAL
FT_LOAD
Hi,
I will appreciate, if someone can give pointers to Load
(FT_LOAD_XXX) and Render(FT_RENDER_XXX) flags to be used in ver. 2.1.10.
Specifically for following scenarios:
-Antialiasing (ON), Hinting(ON)
-Antialiasing (ON), Hinting(OFF)
-Antialiasing (OFF), Hinting(ON)
-Antialias
> > You mean that all registers and operators are based on 8bit entities?
> yes all registers and operators are 8bit.
Hmm, I think there must be at least some 16bit entities for jumps and
similar things, right?
> i don't want to have support for all fonts but if i can compile it
> for a single f
On Fri, 23 Sep 2005 19:34:27 +0530
Kiran Mahajan <[EMAIL PROTECTED]> wrote:
>On Fri, 2005-09-23 at 10:31 +0200, Turner, David wrote:
>> In theory, FreeType should work on 16-bit platforms, but
>> this hasn't been officially verified for a very long time.
>>
>> However, I don't know of any 8-bit p
On Fri, 2005-09-23 at 09:52 +0200, Werner LEMBERG wrote:
> > I want to know that, Is it possible to port freetype2 on 8 bit platform
> > like 8 Bit microcontrollers based on 8051 core or 8 Bit Rabbit
> > processors?
>
> You mean that all registers and operators are based on 8bit entities?
yes all
On Fri, 2005-09-23 at 10:31 +0200, Turner, David wrote:
> In theory, FreeType should work on 16-bit platforms, but
> this hasn't been officially verified for a very long time.
>
> However, I don't know of any 8-bit platform that is capable
> of dealing with, say, memory-mapped files or heap blocks
In theory, FreeType should work on 16-bit platforms, but
this hasn't been officially verified for a very long time.
However, I don't know of any 8-bit platform that is capable
of dealing with, say, memory-mapped files or heap blocks
that are larger than, say, 64 Kb, and this ability is
required to
> - the demo code didn't really select the hinting algorithm
> correctly, I've corrected it in the CVS to match libXft's
> behaviour
Hmm, no ChangeLog entry. Will you do that?
> - there was a bug in the auto-fitter, [...] Fixed in CVS this
> morning before going to work.
No, you didn't.
> I want to know that, Is it possible to port freetype2 on 8 bit platform
> like 8 Bit microcontrollers based on 8051 core or 8 Bit Rabbit
> processors?
You mean that all registers and operators are based on 8bit entities?
This won't work with FreeType unless you have a library which emulates
16b
Hi everyone,
I've got it !
- the demo code didn't really select the hinting algorithm
correctly, I've corrected it in the CVS to match libXft's
behaviour
- there was a bug in the auto-fitter, which never resetted
hint mode bitflags within af_latin_hints_init. The fix is
a one-liner below
> the FreeType API defines several FT_LOAD_TARGET_XXX constants that
> determine which hinting algorithm to use when loading outlines
> from a font file:
>
> FT_LOAD_TARGET_NORMAL => hint for normal anti-aliased rendering
> FT_LOAD_TARGET_LIGHT => same as above, but hint less !
>
> "max_bytes" corresponds to the maximum amount of memory you want to
> dedicate to the cache nodes, it doesn't need to correspond to the
> total memory available on your system; it's used to prevent the
> cache from inflating to vexing levels.
>
> note that it does NOT account for managed FT_Face
Hi all,
Many of you mite have worked on porting Freetype on Embedded platforms.
I want to know that, Is it possible to port freetype2 on 8 bit platform
like 8 Bit microcontrollers based on 8051 core or 8 Bit Rabbit
processors? If yes, which are the facts to do that? Also what will be
the constrains
14 matches
Mail list logo