freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ft-devel] FT_Get_BDF_Property() function does not satisfy LSB standard


From: Chi Nguyen
Subject: [ft-devel] FT_Get_BDF_Property() function does not satisfy LSB standard
Date: Fri, 9 Jan 2009 15:06:26 +0700

To freetype maintainers,

In developing the test for freetype function FT_Get_BDF_Property(), we have
observed the following anomalies:

1) The freetype2 API reference implies that if a given face is from a BDF or
PCF font and if the 'prop_name' is "RESOLUTION_X", the function
FT_Get_BDF_Property() will return 'aproperty' with its type is
'BDF_PROPERTY_TYPE_CARDINAL' and its 'u.cardinal' has correct value.

So when FT_Get_BDF_Property() is called with 'prop_name' is "RESOLUTION_X"
and a given face from PCF font, the function should return 'aproperty' with
its type equal to 'BDF_PROPERTY_TYPE_CARDINAL'.

However, the function returns 'BDF_PROPERTY_TYPE_INTEGER' instead.

2) The freetype2 API reference also implies that if the given face is from a
BDF or PCF font and if the 'prop_name' is "FONT", then if this "FONT" field
exists in the given face, the function FT_Get_BDF_Property() will return
'aproperty' with its type equal to 'BDF_PROPERTY_TYPE_ATOM' and its 'u.atom'
has the correct value as read from the font file using the FontForge
utility.

So when FT_Get_BDF_Property() is called with the given face is from a BDF
font and 'prop_name' is "FONT" and this "FONT" field exists in the given
face, the function should return 'aproperty' with its type equal to
'BDF_PROPERTY_TYPE_ATOM' and 'u.atom' should has the correct value. 

But, the function returned 'BDF_PROPERTY_TYPE_NONE' and 'u.atom' has a value
that does not match the value read from the font file using the FontForge
utility.

Included with this report are:
1) a C programs Example_FT_Get_BDF_Property.c to help reproduce these
behaviors
2) a fonts directory containing the three font files used to demonstrate
these behaviors: 7x13.bdf , Math1.18.pcf and cudevnag12.bdf.

packed in V0015.rar.

We used the FontForge utility to read the expected return values from the
font files.

To reproduce use:

Example_FT_Get_BDF_Property <fully path font file> <property name> <font
type> <u.atom value>

For example:

./Example_FT_Get_BDF_Property fonts/Math1.18.pcf RESOLUTION_X PCF

./Example_FT_Get_BDF_Property fonts/cudevnag12.bdf FONT BDF
"-WRI-Math1-Medium-R-Normal--18-180-75-75-p-100-Adobe-FontSpecific"

./Example_FT_Get_BDF_Property fonts/7x13.bdf FONT BDF
"-Misc-Fixed-Medium-R-Normal--13-120-75-75-C-70-ISO10646-1"


We have tested and reproduced these errors on 32-bit and 64-bit x86 based
test systems running under the following distros OpenSuSE 11 (32 bit),
Ubuntu 8.04 (ia32), RHEL52 x86-64, SLES 10.1 (32bit), Fedora 9 (32bit) with
freetype 2.1.10, freetype 2.3.7 and the current version of CVS as of
07/01/2009.

Thank you very much for your time and please let us know any ruling/finding
that you may have.


Sincerely yours,


Nguyen Trung Chi

Attachment: V0015.rar
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]