headers
Crend King | 1 Oct 2009 08:16
Picon
Favicon
Gravatar

[ft] Can I send/receive FT_*Rec structs via network or RPC?

Hello friends. Recently I'm trying to build a server hosting the 
FreeType library and cache objects, and clients which request the 
rendered character bitmaps from the server. The advantage of doing this 
is the cache in the server is highly shared and reused, and the clients 
are only in charge of implementing the system-specific text out 
procedures. The problem is, sending/receiving the data via network or 
RPC or pipes requires marshaling or serialization. Since there are so 
many embedded pointers in the FT_*Rec structs, and some of them even 
have private members, how do I fully serializing them? Not only do I 
need the final FT_Bitmap, but also I need many metrics and flags stored 
in FT_Face and FT_Size, etc.

One way to solve this problem is to wrap every client-needed field into 
a RPC function, or network request. When the client implementation gets 
more and more complicated, the RPC interface may become messy, and the 
network protocol would be difficult to maintain. Is there any routine 
way to achieve this? I'm really new to FreeType and IPC. Any help is 
appreciated. Thanks!!
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 1 Oct 2009 17:41
Picon

Re: [ft] Can I send/receive FT_*Rec structs via network or RPC?

> Recently I'm trying to build a server hosting the FreeType library
> and cache objects, and clients which request the rendered character
> bitmaps from the server.  The advantage of doing this is the cache
> in the server is highly shared and reused, and the clients are only
> in charge of implementing the system-specific text out procedures.

I think this only works efficiently if you don't use subpixel
rendering...

> The problem is, sending/receiving the data via network or RPC or
> pipes requires marshaling or serialization.  Since there are so many
> embedded pointers in the FT_*Rec structs, and some of them even have
> private members, how do I fully serializing them?  Not only do I
> need the final FT_Bitmap, but also I need many metrics and flags
> stored in FT_Face and FT_Size, etc.

What you want to do is something FreeType hasn't been designed for.

> One way to solve this problem is to wrap every client-needed field
> into a RPC function, or network request.  When the client
> implementation gets more and more complicated, the RPC interface may
> become messy, and the network protocol would be difficult to
> maintain.  Is there any routine way to achieve this?

I don't think so.

    Werner
Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 4 Oct 2009 08:09
Picon

Re: [ft] Defective true type font


> Thanks; Is there a "porting guide" for the demos? I will be porting
> ftview and ftgrid to a small graphics library that isn't
> supported. It has a simple 2D raster type API that I will use to
> render the glyphs (including bitmaps).

You have to port the small `graph' library which is part of the
freetype2-demos bundle; then the rest of the demo programs should link
just fine.  `graph' comes already with support for 6 different OS, so
it shouldn't be too hard to add another one or replace it entirely
with something equivalent.

Note that probably some of the OS support files are no longer
functional; AFAIK, support for Windows and X11 work just fine.

    Werner
Permalink | Reply | 0 comments |
headers
Matt Goebel | 6 Oct 2009 23:37
Picon

[ft] freetype 2.3.9 and recent security warnings?


Hi,

  I was just wondering if the recent security issues with freetype 
affect 2.3.9, and if so, if there is a new version coming out to
address them?

Thanks,
Matt Goebel

--

-- 
Matthew Goebel : goebel <at> emunix.emich.edu : Unix Jockey  <at>  EMU : Hail Eris
Neo-Student, Net Lurker, Donut consumer, and procrastinating Brewer...
 "Always with the negative waves, Moriarty" - Oddball
 "Comfort the troubled, and trouble the comfortable." - Dietrich Bonhoeffer
Permalink | Reply | 2 comments |
headers
mpsuzuki | 8 Oct 2009 06:18
Picon

Re: [ft] freetype 2.3.9 and recent security warnings?

Hi,

On Tue, 6 Oct 2009 17:37:01 -0400 (EDT)
Matt Goebel <goebel <at> emunix.emich.edu> wrote:
>  I was just wondering if the recent security issues with freetype 
>affect 2.3.9, and if so, if there is a new version coming out to
>address them?

Thank you for question about the security issue.

I think most issues are fixed in git, if they
were reported to us with patches. But there might
be "open" issues that were reported without patch,
platform-specific that we could not reproduce, or
not reported to us.

I had better post a summary about the status of
the security issues. Could you recommend some longest
list of FreeType security issues?

Regards,
mpsuzuki
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 8 Oct 2009 07:29
Picon

Re: [ft] freetype 2.3.9 and recent security warnings?

>>  I was just wondering if the recent security issues with freetype 
>>affect 2.3.9, and if so, if there is a new version coming out to
>>address them?
> 
> Thank you for question about the security issue.
> 
> I think most issues are fixed in git, if they
> were reported to us with patches. But there might
> be "open" issues that were reported without patch,
> platform-specific that we could not reproduce, or
> not reported to us.

Freetype 2.3.10 has been already uploaded but not announced yet.  This
follows in a few hours.

    Werner
Permalink | Reply | 0 comments |
headers
Massimo DZ8 | 8 Oct 2009 10:54
Picon

[ft] 2.3.10?

Greetings everyone, I have just downloaded Freetype and signed to the list.

I noticed that on freetype.org the latest version seems to be 2.3.9 
(March 2009), yet on the download area I can find a 2.3.10 (October 2009).
I wonder if the admin just forgot to update freetype.org or there's a 
reason for that. Looking at the changelog, it seems that .10 packs 
mostly internal updates and improvements transparent to me (I will be a 
mere library user). Is this correct?

Have a nice day,
Massimo
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 8 Oct 2009 11:18
Picon

Re: [ft] 2.3.10?


> I noticed that on freetype.org the latest version seems to be 2.3.9
> (March 2009), yet on the download area I can find a 2.3.10 (October
> 2009).
> I wonder if the admin just forgot to update freetype.org or there's a
> reason for that.  [...]

I'm updating everything right now.

    Werner
Permalink | Reply | 0 comments |
headers
Gabriele Brugnoni | 7 Oct 2009 18:38
Picon

[ft] Internal interface patch for sdl-freetype library

Hi,

Referring to the page
http://www.freetype.org/freetype2/freetype-2.2.0.html I send this
patch hoping it might be useful to others.

This patch fix the problem below that may happen when building
sdl-freetype library with newer version of freetype:

In file included from SDL_freetype.c:12:
SDL_freetypeutils.h:17:38: error: freetype/internal/ftobjs.h: No such
file or directory

Regards,
Gabriele Brugnoni.

This is the patch:

diff -ubBrN sdl-freetype-1.0.0-org/src/SDL_freetypeloader.c
sdl-freetype-1.0.0-mdf/src/SDL_freetypeloader.c
--- sdl-freetype-1.0.0-org/src/SDL_freetypeloader.c 2009-10-07
17:46:08.000000000 +0200
+++ sdl-freetype-1.0.0-mdf/src/SDL_freetypeloader.c 2009-10-07
17:46:49.000000000 +0200
 <at>  <at>  -58,7 +58,7  <at>  <at> 
stream->read = SDL_FreeTypeRead;
stream->close = SDL_FreeTypeClose;
stream->descriptor.pointer = RWops;
- stream->memory = SDL_FreeTypeLibrary->memory;
+ stream->memory = NULL;//SDL_FreeTypeLibrary->memory;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Volkov | 10 Oct 2009 18:42
Picon
Favicon

[ft] freetype-2.3.10 regression: font breakage, xine fails

Hi. After bumping freetype-2.3.10 we've received bug report
http://bugs.gentoo.org/288256 stating that PCF fonts in console (urxvt
and kde konsole, gnome-terminal) started to look terrible; kde konsole
shows console8x16.pcf on font list instead of just "Console" (filename
instead of font name). Also xine fails to start (if interested in output
it's documented in bug report). The problem was bissected by Martin von
Gagern to the following commit:

http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=3bda1f9949d20cc46fc76e3876bcff545cc8d665

and reverting it fixed the problem. Is there better fix then reverting
commit? Thanks in advance for you time,
--

-- 
Peter.
Permalink | Reply | 1 comment |

Gmane