Nabble - Freetype - Dev

Re: freetype compilation warnings

2009-12-20T09:20:30Z

>> Just getting rid of _debug_mem_dummy would cause a problem? Is
>> there another way to create a non-empty file? How about a useless
>> but harmless #include, like #include <string.h>?
>
> Ah, I haven't thought of that. Sounds like a good idea.

Well, after some thinking I now believe that this doesn't work: The
preprocessor removes everything and we thus still have an empty file
to compile.

I've now replaced it with a `typedef'.

>> FTC_GNode_Compare() has 2 parameters:
>>
>> FT_LOCAL( FT_Bool )
>> FTC_GNode_Compare( FTC_GNode gnode,
>> FTC_GQuery gquery );
>>
>> but it's being cast to FTC_Node_CompareFunc which is 3 parameters:
>>
>> typedef FT_Bool
>> (*FTC_Node_CompareFunc)( FTC_Node node,
>> FT_Pointer key,
>> FTC_Cache cache );

Yes, this seems to be the cause. However, fixing this is not easy
(except providing a new macro which is rather unelegant) -- at least
for me. Any idea how to work around the warning?

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Extra data for 3D acceleration

2009-12-18T13:54:14Z

> I'm working on code to implement rendering of fonts on a GPU. In
> reality, the fonts will be rendered on the CPU using FreeType2 and a
> texture representing the shape will be sent to the GPU as in the
> paper at alice.loria.fr/publications/papers/2005/VTM/vtm.pdf.

Interesting.

> To do that I need certain information at each pixel. Namely:
>
> 1) Where at the top or left side of the pixel, does the first
> discontinuity occur (If there is more than one discontinuity it will
> increase the resolution until there is only one.)

I'm not completely sure how a `discontinuity' is defined (I've only
quickly skimmed the abovementioned article), but I believe that this
information is not available. The smooth rasterizer only computes
vertical or horizontal spans, that is, it searches for intersections
of the grid with the outlines. If I interpret the article currectly,
this is not sufficient information for you.

> 2) At that point, what is the angle to the tangent of the
> discontinuity.

Ditto.

> 3) Likewise for the bottom or right side of the pixel.

Ditto.

> My plan is to modify the 'grays' raster to generate this data and
> send it to the 'call-back' function where I will create the
> necessary texture for the GPU.

This shouldn't be too hard, I believe, especially if the subdividing
of the Bézier curves as done in the smooth rasterizer satisfies your
needs.

> My assumptions are that the ftgrays AA rasterer is the best choice
> because it has the most data points. (Though the texture map I will
> generate stores only black/white; the GPU will calculate the
> gray/opacity level from the above data.)

In case it doesn't suffice you could use FT_Outline_Decompose,
providing proper callbacks to handle the lines and Bézier arcs by
yourself.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Extra data for 3D acceleration

2009-12-18T08:53:03Z

I'm working on code to implement rendering of fonts on a GPU. In reality, the fonts will be rendered on the CPU using FreeType2 and a texture representing the shape will be sent to the GPU as in the paper at alice.loria.fr/publications/papers/2005/VTM/vtm.pdf.

To do that I need certain information at each pixel. Namely: 1) Where at the top or left side of the pixel, does the first discontinuity occur (If there is more than one discontinuity it will increase the resolution until there is only one.) 2) At that point, what is the angle to the tangent of the discontinuity. 3) Likewise for the bottom or right side of the pixel.

If rastering vertically, I need that info for the sides of the pixel, but if rastering horizontally, I need the info for the points on the top and bottom of the pixel. I don't need both. (See figure 5 in the above paper for a diagram.)

My plan is to modify the 'grays' raster to generate this data and send it to the 'call-back' function where I will create the necessary texture for the GPU.

I have that all set up (raster as StandAlone), and I just need to figure out how to calculate that data. Before I look more closely at how grays_raster is doing its thing, I thought it prudent to seek advice and communicate what I am doing. This weekend/week I will be fiddling with the renderer to discover how to get this data. My assumptions are that the ftgrays AA rasterer is the best choice because it has the most data points. (Though the texture map I will generate stores only black/white; the GPU will calculate the gray/opacity level from the above data.

If anyone is thinking "Oh, that's easy, just use raster X in mode Y and then ....." would you enlighten me?

Thanks,

Bruce

--
Give me immortality or give me death!

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Free type font - query

2009-12-17T21:59:02Z

> We have got the output display in LCD monitor by using the
> freetype-2.3.11 with example1.c with blurred outline.

Yes, this example is very simple to show the most essential basics.

> Regarding the demo code containing gamma corrections, we could not
> see the bitmap information when we run it as standalone.

Ah, perhaps a misunderstanding. I mean the various demo programs in
the `ft2demos-2.3.11' bundle (for Windows it is called ft2dmo2311).
For example, you can control the gamma correction with the keys `G',
`g', and `v' in `ftview'.

> Can u please suggest for any improvements to get the bitmap within
> the mentioned width/height.

Well, FreeType doesn't produce more than 255 gray levels. For
`sharper' images you must not use subpixel positioning (which gives
bad results at small sizes), or you have to use an LCD rendering mode.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-17T08:32:11Z

> I'm afraid it still warns, which doesn't surprise me (I don't think
> changing from enum to #define changes the sign of the constant).

Hmm. An enumeration is implicitly a signed int, whereas I've always
thought that the compiler automatically assigns either signed or
unsigned to (positive) constant values, depending on the other value
of the binop (the `&' in this case). Apparently, this is wrong
thinking.

> Just getting rid of _debug_mem_dummy would cause a problem? Is
> there another way to create a non-empty file? How about a useless
> but harmless #include, like #include <string.h>?

Ah, I haven't thought of that. Sounds like a good idea.

>>> WARNING: While resolving call to function 'FTC_GNode_Compare'
>>> arguments were dropped!
>>
>>This is something I don't understand at all. I have never seen such
>>a warning before, and I have no idea what it means. Can you
>>elaborate?
>
> I'd never seen it either. It's from the llvm compiler.
>
> I _think_ the cause is ftccache.h line 204 (current git):
>
> FTC_Node_CompareFunc _nodcomp = (FTC_Node_CompareFunc)(nodecmp);
>
> FTC_GNode_Compare() has 2 parameters:
>
> FT_LOCAL( FT_Bool )
> FTC_GNode_Compare( FTC_GNode gnode,
> FTC_GQuery gquery );
>
> but it's being cast to FTC_Node_CompareFunc which is 3 parameters:
>
> typedef FT_Bool
> (*FTC_Node_CompareFunc)( FTC_Node node,
> FT_Pointer key,
> FTC_Cache cache );

Thanks for the analysis; will check this soon.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-17T08:04:35Z

On 12/16/09 6:14 PM, Werner LEMBERG said:

>> I don't think your fix was right, the warnings are still there:
>> <http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=494016>
>>
>> Note that those lines have 2 comparisons, not sure which it is
>> complaining about...
>
>OK, hopefully it's now really fixed in git. Please test.

I'm afraid it still warns, which doesn't surprise me (I don't think
changing from enum to #define changes the sign of the constant). Which
compiler do you use? You should be able to repro with gcc's -Wextra or -
Wsign-compare I think.

>> <http://www.cdash.org/CDash/buildSummary.php?buildid=493582>
>> /.../VTK/Utilities/vtkfreetype/src/base/ftdbgmem.c:992: warning:
>> `_debug_mem_dummy' defined but not used
>
>This is expected, more or less:
>
> #if FT_DEBUG_MEMORY
> ...
> #else /* !FT_DEBUG_MEMORY */
>
> /* ANSI C doesn't like empty source files */
> static const FT_Byte _debug_mem_dummy = 0;
>
> #endif /* !FT_DEBUG_MEMORY */
>
>If you know a clean method to avoid the warning, please tell me.

Just getting rid of _debug_mem_dummy would cause a problem? Is there
another way to create a non-empty file? How about a useless but
harmless #include, like #include <string.h>?

>> <http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=493423>
>> WARNING: While resolving call to function 'FTC_GNode_Compare'
>> arguments were dropped!
>
>This is something I don't understand at all. I have never seen such a
>warning before, and I have no idea what it means. Can you elaborate?

I'd never seen it either. It's from the llvm compiler.

I _think_ the cause is ftccache.h line 204 (current git):

FTC_Node_CompareFunc _nodcomp = (FTC_Node_CompareFunc)(nodecmp);

FTC_GNode_Compare() has 2 parameters:

FT_LOCAL( FT_Bool )
FTC_GNode_Compare( FTC_GNode gnode,
FTC_GQuery gquery );

but it's being cast to FTC_Node_CompareFunc which is 3 parameters:

typedef FT_Bool
(*FTC_Node_CompareFunc)( FTC_Node node,
FT_Pointer key,
FTC_Cache cache );

--
____________________________________________________________
Sean McBride, B. Eng sean@...
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Free type font - query

2009-12-17T05:18:27Z

Hi,

Thanks for your suggestions for improving the smoothness of the font.

We have got the output display in LCD monitor by using the freetype-2.3.11
with example1.c with blurred outline.

Regarding the demo code containing gamma corrections, we could not see the
bitmap information when we run it as standalone. Do we need to integrate the
related files in demo code to already existing project, as the gamma
correction related files are missing in freetype-2.3.11?

When we use resolution more than 72 in FT_Set_Char_Size, the received bitmap
width/height exceeds the mentioned width/height but blurring level gets
reduced.

Can u please suggest for any improvements to get the bitmap within the
mentioned width/height.

Thanks and Regards,
Poornima.

-----Original Message-----
From: Werner LEMBERG [mailto:wl@...]
Sent: Wednesday, December 16, 2009 3:18 AM
To: poornima.m@...
Subject: Re: Free type font - query

First of all, please NEVER send images in BMP format! They are
ridiculously large: What you've sent has a size of 2.2MByte. If you
convert this to PNG format, it just takes 16kByte. Maybe this is the
reason for the email delivery failure...

> We have sent this mail to the personal id. Sorry if there is any
> inconvenience.

Please try the email list again for more questions.

> But the outline seems not to be smooth. Please find the image file
> in the attachment for your reference.
>
> Could you please suggest us for any improvements?

I don't have time currently to look at it. Please check our demo
programs, especially ftdiff and ftview, for details.

Just a general remark: If you display white images on black
background, you have to adjust the gamma values to get smoother edges.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-16T23:04:56Z

> <http://www.cdash.org/CDash/buildSummary.php?buildid=493582>
> /.../VTK/Utilities/vtkfreetype/src/base/ftdbgmem.c:992: warning:
> `_debug_mem_dummy' defined but not used

This is expected, more or less:

#if FT_DEBUG_MEMORY
...
#else /* !FT_DEBUG_MEMORY */

/* ANSI C doesn't like empty source files */
static const FT_Byte _debug_mem_dummy = 0;

#endif /* !FT_DEBUG_MEMORY */

If you know a clean method to avoid the warning, please tell me.

> <http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=493423>
> WARNING: While resolving call to function 'FTC_GNode_Compare'
> arguments were dropped!

This is something I don't understand at all. I have never seen such a
warning before, and I have no idea what it means. Can you elaborate?

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-16T09:14:44Z

> I don't think your fix was right, the warnings are still there:
> <http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=494016>
>
> Note that those lines have 2 comparisons, not sure which it is
> complaining about...

OK, hopefully it's now really fixed in git. Please test.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-16T08:38:32Z

On 12/15/09 9:00 AM, Werner LEMBERG said:

>Thanks for the report.
>
>> 4 warnings:
>> <http://www.cdash.org/CDash/buildSummary.php?buildid=493003>
>
>I've fixed them in git.

I don't think your fix was right, the warnings are still there:
<http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=494016>

Note that those lines have 2 comparisons, not sure which it is
complaining about...

--
____________________________________________________________
Sean McBride, B. Eng sean@...
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Free type font - query

2009-12-15T21:53:45Z

Hi,

We are using your TTF open source code for our project GUI. We got success in getting the display of characters in our platform.

But the outline seems not to be smooth. Please find the image file in the attachment for your reference.

Could you please suggest us for any improvements?

Please find the details of our implementation:

* Character height is 20

* working platform – ADI VDSP++

* Output display – LCD monitor through HDMI connector

Kindly let me know if you need more details of our implementation.

Thanks and Regards,

Poornima.M

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

ex1.png (36K) Download Attachment

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-12-15T20:50:35Z

On Tue, 15 Dec 2009 12:33:46 -0500
"Sean McBride" <sean@...> wrote:

>On 11/26/09 6:31 PM, mpsuzuki@... said:
>> http://home.hiroshima-u.ac.jp/mpsuzuki/freetype2-20091126_macslfix.tar.gz
>>
>> * it digs "freetype2" directory. please be careful not
>> * to overwrite your existing "freetype2" directory.
>>
>>Please test it.
>
>I've just tried, and this does seem to fix the problem I reported at the
>start of this thread.

Thank you for checking! Just I've committed the patch to GIT.

Regards,
mpsuzuki

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-12-15T09:33:46Z

On 11/26/09 6:31 PM, mpsuzuki@... said:

>>>Sean, could you review the patch? Yet I don't have access
>>>to Mac OS X 10.6 machines, so I cannot check if this patch
>>>solves the problem you reported.
>
>>I don't know anything about autoconf/automake or even shell script, so
>>I'm not too sure. :(
>
>Oh, I'm sorry. I uploaded a tarball with improved configure at
>
> http://home.hiroshima-u.ac.jp/mpsuzuki/freetype2-20091126_macslfix.tar.gz
>
> * it digs "freetype2" directory. please be careful not
> * to overwrite your existing "freetype2" directory.
>
>Please test it.

I've just tried, and this does seem to fix the problem I reported at the
start of this thread.

Thanks!

--
____________________________________________________________
Sean McBride, B. Eng sean@...
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-15T07:49:29Z

On 12/15/09 9:00 AM, Werner LEMBERG said:

>Thanks for the report.

Thanks for fixing them!

Here are a few more from overnight builds, some warnings are duplicates,
but some are not:

<http://www.cdash.org/CDash/buildSummary.php?buildid=493582>
/.../VTK/Utilities/vtkfreetype/src/base/ftdbgmem.c:992: warning:
`_debug_mem_dummy' defined but not used

<http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=493423>
WARNING: While resolving call to function 'FTC_GNode_Compare' arguments
were dropped!

--
____________________________________________________________
Sean McBride, B. Eng sean@...
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-15T00:00:46Z

Thanks for the report.

> 4 warnings:
> <http://www.cdash.org/CDash/buildSummary.php?buildid=493003>

I've fixed them in git.

> 26 warnings:
> <http://www.cdash.org/CDash/buildSummary.php?buildid=492993>
>
> Some of them look harmless, others look like they should be fixed.

Toshiya-san, please take care of them.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: freetype compilation warnings

2009-12-14T17:37:04Z

Hi,

Thank you for the information, I will check, although
I don't have Microsoft VisualStudio compiler.

BTW, Could you test revised configure (not commited
to git repository yet) for Mac OS X 10.6?
http://lists.gnu.org/archive/html/freetype-devel/2009-11/msg00045.html

Regards,
mpsuzuki

On Mon, 14 Dec 2009 16:31:14 -0500
"Sean McBride" <sean@...> wrote:

>Hi all,
>
>I have just today updated VTK (www.vtk.org) from using freetype 2.3.7 to
>2.3.11. The VTK project has a large number and variety of machines
>doing nightly compilations and some of them are showing compiler
>warnings from freetype.
>
>I'm hoping the freetype devs can look at them, and consider fixing as
>many as reasonable:
>
>4 warnings:
><http://www.cdash.org/CDash/buildSummary.php?buildid=493003>
>
>26 warnings:
><http://www.cdash.org/CDash/buildSummary.php?buildid=492993>
>
>Some of them look harmless, others look like they should be fixed.
>
>Thanks,
>
>--
>____________________________________________________________
>Sean McBride, B. Eng sean@...
>Rogue Research www.rogue-research.com
>
>
>
>
>_______________________________________________
>Freetype-devel mailing list
>Freetype-devel@...
>http://lists.nongnu.org/mailman/listinfo/freetype-devel

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

freetype compilation warnings

2009-12-14T13:31:14Z

Hi all,

I have just today updated VTK (www.vtk.org) from using freetype 2.3.7 to
2.3.11. The VTK project has a large number and variety of machines
doing nightly compilations and some of them are showing compiler
warnings from freetype.

I'm hoping the freetype devs can look at them, and consider fixing as
many as reasonable:

4 warnings:
<http://www.cdash.org/CDash/buildSummary.php?buildid=493003>

26 warnings:
<http://www.cdash.org/CDash/buildSummary.php?buildid=492993>

Some of them look harmless, others look like they should be fixed.

Thanks,

--
____________________________________________________________
Sean McBride, B. Eng sean@...
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Re: [tex-live] Fw: "CMap Resources" open source project

2009-12-08T15:35:47Z

All,

I have some very good news to share. The "Mapping Resources for PDF" open source project, which includes all of the CMap-like mapping resources, went public today. See:

http://opensource.adobe.com/wiki/display/pdfmapping/Mapping+Resources+for+PDF

Enjoy!

-- Dr. Ken Lunde
Senior Computer Scientist, CJKV Type Development
Adobe Systems Incorporated
lunde@...

On 2009/11/15, at 15:12, Albert Astals Cid wrote:

> A Dijous, 24 de setembre de 2009, Ken Lunde va escriure:
>> Karl,
>>
>> I discussed this with the Acrobat team today, and putting the Acrobat
>> mapping files under the same open source license sees very favorable.
>> If I can make it happen, it may take until the end of October for the
>> open source project to go live. I am less then a week away from my
>> annual pronghorn antelope hunt, which involves driving from California
>> to Wyoming, and after that I am attending IUC33. See:
>>
>> http://www.unicodeconference.org/
>>
>> I am giving two presentations, and just started working on them.
>>
>> In any case, I will keep you posted.
>
> How is the open sourcing of Adobe-Japan1-UCS2, GBK-EUC-UCS2, Adobe-GB1-UCS2,
> GBpc-EUC-UCS2, etc. progressing?
>
> Albert
>
>>
>> Regards...
>>
>> -- Ken
>>
>> On 2009/09/23, at 16:25, Karl Berry wrote:
>>> Hi Ken,
>>>
>>>> GBK-EUC-UCS2, Adobe-GB1-UCS2, GBpc-EUC-UCS2, etc. Are they
>>>
>>> If these Acrobat-specific mapping files are to be placed under the
>>> same open source license,
>>>
>>> That would be very desirable.
>>>
>>> I will need to work with the Acrobat development team. I would
>>> prefer that they be included in a separate open source project.
>>>
>>> However it works best for you.
>>>
>>> We greatly appreciate all your efforts!
>>>
>>> Thanks,
>>> Karl
>>
>> _______________________________________________
>> Freetype-devel mailing list
>> Freetype-devel@...
>> http://lists.nongnu.org/mailman/listinfo/freetype-devel
>>
>

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Fwd: FreeType patented bytecode interpreter now in rawhide

2009-12-03T16:14:03Z

FYI.

-------- Original Message --------
Subject: FreeType patented bytecode interpreter now in rawhide
Date: Thu, 03 Dec 2009 19:13:42 -0500
From: Behdad Esfahbod <behdad@...>
To: Development discussions related to Fedora <fedora-devel-list@...>,
fedora-fonts-list <fedora-fonts-list@...>

Hi,

Since the patents covering the TrueType bytecode interpreter expired at the
end of October, I've now built FreeType in rawhide with that part of code enabled.

Note that the subpixel stuff remains disabled as it was.

behdad

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Free tyep font - query

2009-11-30T22:09:29Z

> (1) We couldn't be successful in getting display of more than one
> character. The characters gets overlapped.

Uh, oh, this is basic programming... You've modified the source
without thinking:

draw_bitmap( FT_Bitmap* bitmap,
FT_Int x,
FT_Int y)
{
FT_Int i, j, p, q;
FT_Int x_max = x + bitmap->width;
FT_Int y_max = y + bitmap->rows;

-
+ width = bitmap->width;
+ rows = bitmap->rows;
for ( i = x, p = 0; i < x_max; i++, p++ )
{
for ( j = y, q = 0; j < y_max; j++, q++ )
{
if ( i < 0 || j < 0 ||
i >= WIDTH || j >= HEIGHT )
continue;

- image[j][i] |= bitmap->buffer[q * bitmap->width + p];
+ image[q][p] |= bitmap->buffer[q * bitmap->width + p]; <<<<< wrong!
}
}
+
+ printf("\n Bitmap Width %d",width);
+ printf("\n Bitmap Height %d",rows);
+ printf("\n Width %d",p);
+ printf("\n Height %d\n",q);
}

The marked line causes your problems since you ignore any offset given
by x and y.

> (2) Since height and width of each character gets varied, how the
> starting position of drawing the next character be found.

The original example1.c code works just fine and does the expected!
Why not checking it carefully? The position of the next glyph is
controlled by the last glyph's advance width (and height). All these
details are discussed in the tutorial and the other documentation
files.

> It will be helpful if you support us as early as possible.

As others have already mentioned, this attitude is inappropriate for a
library which you are using for free, without any fees, and where
everyone is working as a volunteer in his sparetime.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Free tyep font - query

2009-11-30T10:37:30Z

"jeyasathya" <Jeyasathya.j@...> wrote:

> It will be helpful if you support us as early as possible. Kindly let me
> know if queries is not clear.

This is not really a place for this kind of queries. Freetype project
already provides you with sample code and documentation. If you can't
understand what that code does or how to change it for your own needs
that's a different problem which doesn't belong here.

--
Dmitry.

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Free tyep font - query

2009-11-30T05:34:58Z

Dear all,

We are using True type Font library delivered by you for our project. As a first step we are using VC++.

By using the exampl1.c file we have got display of a single character.

Could you please give your valuable suggestions for the following queries?

(1) We couldn't be successful in getting display of more than one character. The characters gets

overlapped.

(2) Since height and width of each character gets varied, how the starting position of drawing the next character be found.

It will be helpful if you support us as early as possible. Kindly let me know if queries is not clear.

Note: I have attached the example1.c file for your reference.

Thanks and Regards

Jeyasathya

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

example1.c (4K) Download Attachment

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-26T01:31:44Z

On Wed, 25 Nov 2009 19:26:05 -0500
"Sean McBride" <sean@...> wrote:
>On 11/18/09 7:00 PM, mpsuzuki@... said:
>>Sean, could you review the patch? Yet I don't have access
>>to Mac OS X 10.6 machines, so I cannot check if this patch
>>solves the problem you reported.

>I don't know anything about autoconf/automake or even shell script, so
>I'm not too sure. :(

Oh, I'm sorry. I uploaded a tarball with improved configure at

http://home.hiroshima-u.ac.jp/mpsuzuki/freetype2-20091126_macslfix.tar.gz

* it digs "freetype2" directory. please be careful not
* to overwrite your existing "freetype2" directory.

Please test it.

Regards,
mpsuzuki

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-26T01:27:46Z

Dear Rowan,

Great Thank you for spending time to confirm!

On Thu, 26 Nov 2009 15:04:26 +1300
Rowan Wookey <admin@...> wrote:
>Here is the new output in the configure script
>
>checking whether CFLAGS and LDFLAGS share -arch i386... no, copy to LDFLAGS
>checking whether CFLAGS and LDFLAGS share -isysroot /Developer/SDKs/MacOSX10.5.sdk... no, copy to LDFLAGS

Good, it's what I designed.

>2) The patch looks like it has been word wrapped on line 47 to have " .*//'`" (without quotes) just move this up to line 46 preserving the space at the beginning so line 46 should be:
>- isysroot_dir=`echo ${CFLAGS} | tr '\t' ' ' | sed 's/^.*-isysroot *//;s/ .*//'`

Oops, I should not put the patch in the text
which can be folded by some MUA. I'm sorry
for troubling you.

Regards,
mpsuzuki

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-25T18:04:26Z

I can confirm this works.

I configured as if building for OS X 10.5 as 32 bit, on OS X 10.6 with the default compiler setting at 64 bit.

Here is the new output in the configure script

checking whether CFLAGS and LDFLAGS share -arch i386... no, copy to LDFLAGS
checking whether CFLAGS and LDFLAGS share -isysroot /Developer/SDKs/MacOSX10.5.sdk... no, copy to LDFLAGS

A few notes
1) I had to edit autogen.sh to allow autoconf 2.61 and aclocal 1.10 which are the versions supplied with OS X 10.6
2) The patch looks like it has been word wrapped on line 47 to have " .*//'`" (without quotes) just move this up to line 46 preserving the space at the beginning so line 46 should be:
- isysroot_dir=`echo ${CFLAGS} | tr '\t' ' ' | sed 's/^.*-isysroot *//;s/ .*//'`
3)My CFLAGS were set to CFLAGS="-arch i386 -pipe -Os -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5"
4) file libfreetype.6.dylib outputs : "libfreetype.6.dylib: Mach-O dynamically linked shared library i386" which is correct.
5) I used the latest development version from git.

Regards

Rowan

On 26 Nov 2009, at 13:26, Sean McBride wrote:

> On 11/18/09 7:00 PM, mpsuzuki@... said:
>
>> I'm not sure if there is special
>> requirement to use different "-arch XXX" or "-m32/-m64"
>> options between CFLAGS & LDFLAGS.
>>
>> Sean, could you review the patch? Yet I don't have access
>> to Mac OS X 10.6 machines, so I cannot check if this patch
>> solves the problem you reported.
>
> Sorry for the delayed reply.
>
> I don't know anything about autoconf/automake or even shell script, so
> I'm not too sure. :(
>
> But I do know that -m32 and -m64 are not used on OS X. It's really just
> -arch that controls that.
>
> Thanks,
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng sean@...
> Rogue Research www.rogue-research.com
> Mac Software Developer Montréal, Québec, Canada
>
>

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-25T16:26:05Z

On 11/18/09 7:00 PM, mpsuzuki@... said:

>I'm not sure if there is special
>requirement to use different "-arch XXX" or "-m32/-m64"
>options between CFLAGS & LDFLAGS.
>
>Sean, could you review the patch? Yet I don't have access
>to Mac OS X 10.6 machines, so I cannot check if this patch
>solves the problem you reported.

Sorry for the delayed reply.

I don't know anything about autoconf/automake or even shell script, so
I'm not too sure. :(

But I do know that -m32 and -m64 are not used on OS X. It's really just
-arch that controls that.

Thanks,

--
____________________________________________________________
Sean McBride, B. Eng sean@...
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-25T15:00:36Z

> Attached is a proposal of patch for Mac OS X 10.6.

If you think this is the right way to go please commit.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Cross compiling free type 2 for Arm development boards

2009-11-19T02:39:03Z

Hi

My name is Basil. I am trying to port the freetype library to a arm development board. I am using the arm cross compiler executable
arm-none-linux-gnueabi and i followed the instructions in INSTALL.CROSS but i am unable to create a configuration file for freetype.

This is the input i have given
basil@Bas:~/Desktop/Freetype/freetype-2.3.11$ ./configure --build=i686-pc-linux-gnu --host=arm-none-linux-gnueabi

The output i got was

FreeType build system -- automatic system detection

The following settings are used:

platform                    unix
compiler                    cc
configuration directory     ./builds/unix
configuration rules         ./builds/unix/unix.mk

If this does not correspond to your system or settings please remove the file
`config.mk' from this directory then read the INSTALL file for help.

Otherwise, simply type `make' again to build the library,
or `make refdoc' to build the API reference (the latter needs python).

cd builds/unix; ./configure '--build=i686-pc-linux-gnu' '--host=arm-none-linux-gnueabi'
checking build system type... i686-pc-linux-gnu
checking host system type... arm-none-linux-gnueabi
checking for arm-none-linux-gnueabi-gcc... arm-none-linux-gnueabi-gcc
checking for C compiler default output file name...
configure: error: in `/home/basil/Desktop/Freetype/freetype-2.3.11/builds/unix':
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** [setup] Error 77

Kindly let me know whether i am missing any step in the process

--
The end is only the beginning

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-18T02:00:39Z

Hi,

Sorry for my lated homework. Attached is a proposal of
patch for Mac OS X 10.6. The patch itself is not easy
to read. The patched script would be like following.
It scans all token in CFLAGS, lookup -isysroot, -arch,
-m32 and -m64. If they are not included in LDFLAGS
(for -isysroot and -arch, arguments are also checked),
they are copied to LDFLAGS.

# Some options handling SDKs/archs in CFLAGS should be copied
# to LDFLAGS. Apple TechNote 2137 recommends to include these
# options in CFLAGS but not in LDFLAGS.

set dummy ${CFLAGS}
i=1
while test $i -lt $#
do
c=$1

case "${c}" in
-isysroot|-arch) # options taking 1 argument
a=$2
AC_MSG_CHECKING([whether CFLAGS and LDFLAGS share ${c} ${a}])
if expr " ${LDFLAGS} " : ".* ${c} *${a}.*" > /dev/null
then
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no, copy to LDFLAGS])
LDFLAGS="${LDFLAGS} ${c} ${a}"
fi
shift 1
;;
-m32|-m64) # options taking no argument
AC_MSG_RESULT([whether CFLAGS and LDFLAGS share ${c}])
if expr " ${LDFLAGS} " : ".* ${c} *${a}.*" > /dev/null
then
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no, copy to LDFLAGS])
LDFLAGS="${LDFLAGS} ${c}"
fi
;;
# *)
# AC_MSG_RESULT([${c} is not copied to LDFLAGS])
# ;;
esac

shift 1
done

At present, I didn't restrict this hook to specific
system. If it's better to restrict this hook to Mac OS X,
please let me know. I'm not sure if there is special
requirement to use different "-arch XXX" or "-m32/-m64"
options between CFLAGS & LDFLAGS.

Sean, could you review the patch? Yet I don't have access
to Mac OS X 10.6 machines, so I cannot check if this patch
solves the problem you reported.

Regards,
mpsuzuki

diff --git a/builds/unix/configure.raw b/builds/unix/configure.raw
index 8a99988..4ecd619 100644
--- a/builds/unix/configure.raw
+++ b/builds/unix/configure.raw
@@ -230,30 +230,48 @@ if test x$with_zlib != xno && test -n "$LIBZ"; then
fi

-# check Apple's `-isysroot' option and duplicate it to LDFLAGS if required --
-# Apple TechNote 2137 recommends to include it in CFLAGS but not in LDFLAGS
-
-AC_MSG_CHECKING([whether CFLAGS includes -isysroot option])
-case "$CFLAGS" in
-*sysroot* )
- AC_MSG_RESULT([yes])
- AC_MSG_CHECKING([whether LDFLAGS includes -isysroot option])
- case "$LDFLAGS" in
- *sysroot* )
- AC_MSG_RESULT([yes])
+# Some options handling SDKs/archs in CFLAGS should be copied
+# to LDFLAGS. Apple TechNote 2137 recommends to include these
+# options in CFLAGS but not in LDFLAGS.
+
+save_config_args=$*
+set dummy ${CFLAGS}
+i=1
+while test $i -lt $#
+do
+ c=$1
+
+ case "${c}" in
+ -isysroot|-arch) # options taking 1 argument
+ a=$2
+ AC_MSG_CHECKING([whether CFLAGS and LDFLAGS share ${c} ${a}])
+ if expr " ${LDFLAGS} " : ".* ${c} *${a}.*" > /dev/null
+ then
+ AC_MSG_RESULT([yes])
+ else
+ AC_MSG_RESULT([no, copy to LDFLAGS])
+ LDFLAGS="${LDFLAGS} ${c} ${a}"
+ fi
+ shift 1
;;
- *)
- AC_MSG_RESULT([no])
- isysroot_dir=`echo ${CFLAGS} | tr '\t' ' ' | sed 's/^.*-isysroot *//;s/ .*//'`
- AC_MSG_WARN(-isysroot ${isysroot_dir} is added to LDFLAGS)
- LDFLAGS="-isysroot ${isysroot_dir} ${LDFLAGS}"
+ -m32|-m64) # options taking no argument
+ AC_MSG_RESULT([whether CFLAGS and LDFLAGS share ${c}])
+ if expr " ${LDFLAGS} " : ".* ${c} *${a}.*" > /dev/null
+ then
+ AC_MSG_RESULT([yes])
+ else
+ AC_MSG_RESULT([no, copy to LDFLAGS])
+ LDFLAGS="${LDFLAGS} ${c}"
+ fi
;;
+ # *)
+ # AC_MSG_RESULT([${c} is not copied to LDFLAGS])
+ # ;;
esac
- ;;
-*)
- AC_MSG_RESULT([no])
- ;;
-esac
+
+ shift 1
+done
+set ${save_config_args}

# Whether to use Mac OS resource-based fonts.

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Re: [tex-live] Fw: "CMap Resources" open source project

2009-11-15T15:42:16Z

Albert,

Your email is *very* timely, because it was on Friday (11/13/2009)
that the Acrobat team gave the proverbial "green light" to open-source
these mapping resources.

Anyway, I plan to spend the better part of the coming week preparing
the files, which primarily amounts to adding the open source license
to the headers of each file. The tentative name of the open source
project is "Mapping Resources for PDF."

BTW, you might find the following forum thread to be helpful:

http://forums.adobe.com/message/2277338

With best regards...

-- Ken

On 2009/11/15, at 15:12, Albert Astals Cid wrote:

> A Dijous, 24 de setembre de 2009, Ken Lunde va escriure:
>> Karl,
>>
>> I discussed this with the Acrobat team today, and putting the Acrobat
>> mapping files under the same open source license sees very favorable.
>> If I can make it happen, it may take until the end of October for the
>> open source project to go live. I am less then a week away from my
>> annual pronghorn antelope hunt, which involves driving from
>> California
>> to Wyoming, and after that I am attending IUC33. See:
>>
>> http://www.unicodeconference.org/
>>
>> I am giving two presentations, and just started working on them.
>>
>> In any case, I will keep you posted.
>
> How is the open sourcing of Adobe-Japan1-UCS2, GBK-EUC-UCS2, Adobe-
> GB1-UCS2,
> GBpc-EUC-UCS2, etc. progressing?
>
> Albert
>
>>
>> Regards...
>>
>> -- Ken
>>
>> On 2009/09/23, at 16:25, Karl Berry wrote:
>>> Hi Ken,
>>>
>>>> GBK-EUC-UCS2, Adobe-GB1-UCS2, GBpc-EUC-UCS2, etc. Are they
>>>
>>> If these Acrobat-specific mapping files are to be placed under the
>>> same open source license,
>>>
>>> That would be very desirable.
>>>
>>> I will need to work with the Acrobat development team. I would
>>> prefer that they be included in a separate open source project.
>>>
>>> However it works best for you.
>>>
>>> We greatly appreciate all your efforts!
>>>
>>> Thanks,
>>> Karl
>>
>> _______________________________________________
>> Freetype-devel mailing list
>> Freetype-devel@...
>> http://lists.nongnu.org/mailman/listinfo/freetype-devel
>>
>

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Re: [tex-live] Fw: "CMap Resources" open source project

2009-11-15T15:12:07Z

A Dijous, 24 de setembre de 2009, Ken Lunde va escriure:

> Karl,
>
> I discussed this with the Acrobat team today, and putting the Acrobat
> mapping files under the same open source license sees very favorable.
> If I can make it happen, it may take until the end of October for the
> open source project to go live. I am less then a week away from my
> annual pronghorn antelope hunt, which involves driving from California
> to Wyoming, and after that I am attending IUC33. See:
>
> http://www.unicodeconference.org/
>
> I am giving two presentations, and just started working on them.
>
> In any case, I will keep you posted.

How is the open sourcing of Adobe-Japan1-UCS2, GBK-EUC-UCS2, Adobe-GB1-UCS2,
GBpc-EUC-UCS2, etc. progressing?

Albert

>
> Regards...
>
> -- Ken
>
> On 2009/09/23, at 16:25, Karl Berry wrote:
> > Hi Ken,
> >
> >> GBK-EUC-UCS2, Adobe-GB1-UCS2, GBpc-EUC-UCS2, etc. Are they
> >
> > If these Acrobat-specific mapping files are to be placed under the
> > same open source license,
> >
> > That would be very desirable.
> >
> > I will need to work with the Acrobat development team. I would
> > prefer that they be included in a separate open source project.
> >
> > However it works best for you.
> >
> > We greatly appreciate all your efforts!
> >
> > Thanks,
> > Karl
>
> _______________________________________________
> Freetype-devel mailing list
> Freetype-devel@...
> http://lists.nongnu.org/mailman/listinfo/freetype-devel
>

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: building freetype 2.3.11 on Mac OS X 10.6

2009-11-13T06:29:01Z

Hi,

Thank you for helpful information. I will propose
improved configure script in next week...

Regards,
mpsuzuki

On Fri, 13 Nov 2009 08:16:03 +1300
Rowan Wookey <admin@...> wrote:

>
>Try adding the arch flag to LDFLAGS that worked for me.
>
>~Rowan
>
>
>_______________________________________________
>Freetype-devel mailing list
>Freetype-devel@...
>http://lists.nongnu.org/mailman/listinfo/freetype-devel

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Porting FT2

2009-11-13T05:48:45Z

> 1. I have compiled the "freetype-2.3.11" in VC++ it gives the out
> put file as *.dlb. But I want it as *.exe

??? FreeType is a *library*, not an executable!

> 2. I couldn't find any proper main function to start from there.

Of course not. See my other reply.

> 3. Is there any main function for test purpose? With the input file
> path and character code and output as pixel data?

In the ft2demos bundle you can find a bunch of test programs. The
tutorial from www.freetype.org also provides some demo programs.

> 4. There are lots of APIs in the documentation. I am not getting
> idea, what are all the APIs needed for simple true type font
> display.

Uff. You are joking, aren't you? You are coming from India and you
want `simple' TTF display? For complex scripts like Devanagari you
need a complete shaping engine, for example the ICU, Qt, or Pango
libraries.

What about reading the tutorial first? This shows examples of simple
usage for non-complex scripts.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: Porting FT2

2009-11-13T05:45:02Z

> Also as it said in, "II. Modules list" of CUSTOMIZE, I have commented
> manually every thing except
>
> "FT_USE_MODULE( FT_Driver_ClassRec, tt_driver_class )"

This doesn't suffice. You need a graphics renderer too, either the
b/w rasterizer or the aliasing one.

> I want one main function, with in that function what are all
> should I call? So I can give my file path name for getting pixel
> data?

There isn't a single function. You have to initialize FreeType, load
a font, select a glyph, and finally finalize FreeType. Please check
the `ftview' demo program, for example.

Werner

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel

RE: Porting FT2

2009-11-13T03:19:24Z

Dear all,

Now I have planned to work with VC++ first then I will extend it to my own
platform (VDSP environment/Blackfin processor), for that I am having the
following basic doubts, please clarify...

My aim is I want to use TTF font for my project GUI display.

1. I have compiled the "freetype-2.3.11" in VC++ it gives the out put file
as *.dlb. But I want it as *.exe

2. I couldn't find any proper main function to start from there.

3. Is there any main function for test purpose? With the input file path and
character code and output as pixel data?

4. There are lots of APIs in the documentation. I am not getting idea, what
are all the APIs needed for simple true type font display.

Kindly advice.

Best regards,
Kumar.K

-----Original Message-----
From: mpsuzuki@... [mailto:mpsuzuki@...]
Sent: Thursday, November 12, 2009 3:29 PM
To: Kumar.K
Cc: wl@...; freetype-devel@...
Subject: Re: [ft-devel] Porting FT2

Hi,

The naming conventions of the files are:

When the version of freetype2 is L.M.N (in this case, L=2, M=3, N=11)

freetype-L.M.N.tar.gz tar+gzip archived source (for Unix, Mac OS
X)
freetype-L.M.N.tar.gz.sig checksum for tar+gzip source
freetype-L.M.N.tar.bz2 tar+bzip2 archived (for Unix, Mac OS X)
freetype-L.M.N.tar.bz2.sig checksum for tar+bzip2 source
ftLMN.zip zip archived source (for Win32)
ftLMN.zip.sig checksum for zip archived source

ft2demos-L.M.N.tar.gz tar+gzip archived demo program source
ft2demos-L.M.N.tar.gz.sig checksum for tar+gzip archived demo
ft2demos-L.M.N.tar.bz2 tar+bzip2 archived demo program source
ft2demos-L.M.N.tar.bz2.sig checksum for tar+bzip2 archived demo
ftdmoLMN.zip zip archived demo program source
ftdmoLMN.zip.sig checksum for zip archived demo program
source

freetype-doc-L.M.N.tar.gz tar+gzip archived document
freetype-doc-L.M.N.tar.gz.sig checksum for tar+gzip archived document
freetype-doc-L.M.N.tar.bz2 tar+bzip2 archived document
freetype-doc-L.M.N.tar.bzip2.sig checksum for tar+bzip2 archived
document
ftdocLMN.zip zip archived document
ftdocLMN.zip.sig checksum for zip archived document

I don't know the detail development environment, and
your favorite archiver, so I cannot tell you exact files.

If your development environment prefers the sources
terminated with Win32-like CR/LF, zip files might be better.

Regards,
mpsuzuki

On Thu, 12 Nov 2009 14:41:32 +0530
"Kumar.K" <kumar.k@...> wrote:

>Hi,
> I want the latest version and its documentation, demo and its
>related files I found these following links,
>
>http://savannah.inetbridge.net/freetype/
>
>http://sourceforge.net/projects/freetype/files/

On Thu, 12 Nov 2009 14:41:32 +0530
"Kumar.K" <kumar.k@...> wrote:

>Hi,
> I want the latest version and its documentation, demo and its
>related files I found these following links,
>
>http://savannah.inetbridge.net/freetype/
>
>http://sourceforge.net/projects/freetype/files/
>
>
>In the above page link there are lot of zip files and other format files.
>Can you give me the correct links?
>
>
>
>
>Best regards,
>Kumar.K
>
>-----Original Message-----
>From: Werner LEMBERG [mailto:wl@...]
>Sent: Thursday, November 12, 2009 12:57 AM
>To: kumar.k@...
>Cc: freetype-devel@...
>Subject: Re: [ft-devel] Porting FT2
>
>
>> I want to port FT 2 to my application. We are working in analog
>> devices Blackfin processor, and using its IDE -VDK. I want to use
>> only true type font for my project. Can you tell where should I
>> start? Actually I am struggling .
>
>Please read the files INSTALL.ANY and CUSTOMIZE (in the `docs'
>subdirectory) and look up the mailing list archives of both freetype
>and freetype-devel since this is a rather popular question.
>
>
> Werner
>
>
>
>
>_______________________________________________
>Freetype-devel mailing list
>Freetype-devel@...
>http://lists.nongnu.org/mailman/listinfo/freetype-devel

_______________________________________________
Freetype-devel mailing list
Freetype-devel@...
http://lists.nongnu.org/mailman/listinfo/freetype-devel