[ft] help needed for retrieving design metrics

Hello,

yesterday I started looking into FT to evaluate its use.

While that I'm trying to extract design values I know from FontForge and
FontLab the Font has.

For example a glyph "A" of a font it shows a box with width 660 while
the serifs to the left and to the right linger over the box, -23 to the
left and -23 to the right.
For an "e" it's different, there the box is 500 width and the glyphs
borders are 40 inside on the left and 44 on the right side.

Now FT_Load_Glyph() width FT_LOAD_NO_SCALE gives the following:

metrics.horiAdvance:  65, metrics.width: 660, metrics.horiBearingX: 706
metrics.horiAdvance: 101, metrics.width: 500, metrics.horiBearingX: 416

Ok, width is right. And width-horiBearingX equals the sum of the above
numbers. But what's horiAdvance in no-scale-terms?. And how to access
the individual numbers for the distances?

Regards,
Jürgen

[ft] Use of a Chinese font

Hello,

I intend to use chinese characters, in my own device using Freetype.
But a basical chinese ttf font is near 10 Mo.
I haven't enought memory to store it and use with FT.

I'm looking for a way to have the smallest font :
- with compression : Does someone know a process or an algorithm to reduce 
data size and to link with Freetype : decompression when opening the font or 
a linear process character by character?
what will be the size profit?
- Use of another font file format ?

Any other ideas?

Thanks you very much, for your help.

Regards,
Thomas
_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

_________________________________________________________________
Windows Live Spaces : créez votre blog à votre image ! 
http://www.windowslive.fr/spaces

Re: [ft] Use of a Chinese font

> I intend to use chinese characters, in my own device using Freetype.
> But a basical chinese ttf font is near 10 Mo.

Not necessarily.  The good old mingli.ttf, version 1.00 from 1992
covers the complete Big5 character set and has 2,86MByte.

> I haven't enought memory to store it and use with FT.

Depending on your device it might be better to use a bitmap-only font
(using the SFNT container format), containing some strikes for
selected sizes, say, 14x14, 16x16, etc.

> I'm looking for a way to have the smallest font :
>
> - with compression: Does someone know a process or an algorithm to
> reduce data size and to link with Freetype : decompression when
> opening the font or a linear process character by character?

Well, TrueType instructions are already quite dense; similarly, the
storage format for bitmaps within the SFNT container format is quite
compact also.

    Werner

[ft] Anti-aliasing issues with freetype 2.3.1 (ppc cross-compiled)

Hello all.

I'm working on this issue for several days now and can't find the cause of a 
very annoying bug in anti-aliased font rendering, so I'm asking here as I 
think there are people on this list who at least know the freetype code. :)

So, the problem is in rendering anti-aliased fonts on embedded board 
(PowerPC platform). Freetype is cross-compiled here, I'm using GCC 3.4.3, 
but it's a really stable toolchain, known to compile a lot of things 
without any issues.

I'm compiling it via RPM, it exports CC/CXX/AS/LD/AR/OBJCOPY and some other 
environment variables and issues the following command:

./configure --host=ppc-unknown-linux-gnu --build=i686-pc-linux-gnu --target=pp
c-unknown-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=
/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir
=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var -
-sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info

Freetype self-configures the following way:

The following settings are used:

  platform                    unix
  compiler                    ppc_82xx-gcc
  configuration directory     ./builds/unix
  configuration rules         ./builds/unix/unix.mk

If this does not correspond to your system or settings please remove the 

Re: [ft] Anti-aliasing issues with freetype 2.3.1 (ppc cross-compiled)

> I'm working on this issue for several days now and can't find the
> cause of a very annoying bug in anti-aliased font rendering, so I'm
> asking here as I think there are people on this list who at least
> know the freetype code. :)

May it's helpful to compare the output of the logging messages
activated with the `FT2_DEBUG' environment variable.  The higher the
debugging level, the more verbose the messages.  See docs/DEBUG for
more details.

    Werner

Re: [ft] Anti-aliasing issues with freetype 2.3.1 (ppc cross-compiled)

Werner LEMBERG:
> > I'm working on this issue for several days now and can't find the
> > cause of a very annoying bug in anti-aliased font rendering, so I'm
> > asking here as I think there are people on this list who at least
> > know the freetype code. :)
>
> May it's helpful to compare the output of the logging messages
> activated with the `FT2_DEBUG' environment variable.  The higher the
> debugging level, the more verbose the messages.  See docs/DEBUG for
> more details.

Thanks for suggestion.

I've did that with FT2_DEBUG set to "any:6" and results are available here:

target:	http://roman.khimov.ru/temp/freetype/debug.out
host:	http://roman.khimov.ru/temp/freetype/debug-host.out

I've looked through diff and couldn't find anything other than obvious 
path/memory addresses difference... :-/

--

-- 
                            Roman
 http://roman.khimov.ru                                              .o.
mailto: roman <at> khimov.ru                                              ..o
gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3         ooo

_______________________________________________
Freetype mailing list

[ft] Problems using Freetype on Pocket PC 2003

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

[ft] retrieving kerning infos misbehaves

Hello,

I currently try getting kerning to work - but it doesn't work always.

It's weird, the first call to FT_Get_Kerning() always fills in the right
value for a kerning pair, regardless of any flag.

After a call to FT_Load_Glyph() later calls to FT_Get_Kerning() only
give the right value if it has FT_KERNING_UNFITTED or
FT_KERNING_UNSCALED set. Or when called with FT_KERNING_DEFAULT if
FT_Load_Glyph() has FT_LOAD_NO_HINTING or FT_LOAD_NO_SCALE (which
includes FT_LOAD_NO_HINTING) set.

But is FT_KERNING_DEFAULT set in FT_Get_Kerning() and FT_Load_Glyph()
has either FT_LOAD_DEFAULT, FT_LOAD_RENDER or FT_LOAD_NO_BITMAP set,
kerning infos are always 0.

I'm using Freetype 2.21 but have it also tested with 2.31.

Any ideas what that is?

Regards,
Jürgen

[ft] Re: Anti-aliasing issues with freetype 2.3.1 (ppc cross-compiled)

Roman I Khimov:
> I'm working on this issue for several days now and can't find the cause
> of a very annoying bug in anti-aliased font rendering, so I'm asking here
> as I think there are people on this list who at least know the freetype
> code. :)

I've investigated it further and most probably it's not a freetype issue. 
Bug is only triggered with remote X, native rendering makes perfect 
picture.

Thanks all and sorry for the noise.

--

-- 
                            Roman
 http://roman.khimov.ru                                              .o.
mailto: roman <at> khimov.ru                                              ..o
gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3         ooo

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

[ft] question on FT number formats

Hello all,

I don't understand what 16.16 and 26.6 formats are
that FT uses or furthermore how users of FT are
affected by that.

I guess a problem I have getting kerning from Type1
fonts lies in the numbers format.

Loading a Type1 font and attaching an afm file works
as it should. But attaching a pfm file produces huge
kerning distances of 372672 or 372480 instead ones
like -192 or -320.

That's for all Type1 fonts I have tried from various
sources, so I guess there's some error on my side.
Have you an idea what?

Johannes

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de