Subject: Fwd: gnome-print & fonts
From: Leonard Rosenthol (leonardr@lazerware.com)
Date: Tue Feb 06 2001 - 11:08:07 CST
From one of the gnome-print guys about font issues and how they
addressed certain things. Sounds like there might be some code there
worth looking at given our recent discussions about fonts & printing.
Leonard
_____________________________
>Delivered-To: libart@gnome.org
>Subject: Re: [LIBART] type 1 fonts
>From: Lauris Kaplinski <lauris@ximian.com>
>To: Robin Becker <robin@jessikat.fsnet.co.uk>
>Cc: libart@gnome.org, gnome-print@helixcode.com
>Date: 06 Feb 2001 16:16:53 +0200
>Sender: libart-admin@gnome.org
>X-BeenThere: libart@gnome.org
>X-Loop: libart@gnome.org
>X-Mailman-Version: 2.0beta5
>List-Id: Using and integrating the Libart 2D imaging lib <libart.gnome.org>
>
>Hello!
>
>On 06 Feb 2001 12:47:44 +0000, Robin Becker wrote:
>> I'm not sure if this is the right list to ask, but I'm sure someone will
>> set me straight if not.
>
>The right place for libgt1/gnome-font/... things should be
>gnome-print@helixcode.com
>
>> I'm trying to make use of the type 1 library stuff in gnome-
>> font/libgnomefont/gt1
>>
>> 1) Trawling the sources I seem to find that this handles loading of
>> fonts from pfb files with metric info from afm files. The standard Adobe
>> stuff on my win32 box comes with pfm files. Is there any interest in
>> being able to read the equivalent information from pfms?
>>
>> 2) The gt1_load_font procedure seems to read the font and build up three
>> different encoding vectors and then throws two of these away. Wouldn't
>> it be better to split off the encoding builder into a separate routine.
>> Also we seem to ignore the Symbol encoding which is very useful.
>
>The gnome-font procedures are highly experimental and far from
>stable enough to use.
>I have used these, to test several ideas, how to arrange font-handling for
>gnome-print. Currently gnome-print has working copy of gnome-font
>functionality,
>with the exception of FreeType stuff. So if you are interested in Type1 fonts,
>I suggest better looking there.
>For example, in gnome-print I dropped 8 bit encoding vectors
>completely - instead
>we create unicode <-> glyph mapping, which includes currently Adobe symbols in
>addition to latin, greek and cyrillic characters.
>
>As of pfms, I do not know, whether reading these directly will make
>sense. Maybe
>we could include pfm -> afm converter with gnome-print.
>
>Btw. I have plan to replace libgt1 in gnome-print with FreeType2
>eventually - the
>main obstacle has been the unavailablility of FreeType2 installable
>version. That
>is not problem any more, but at moment I do not want to do so big modification
>before gnome-1.4 any more.
>Also, unfortunately, FreeType2 functionality is not sufficent, so
>there have to remain
>separate Type1 reading procedures, FT2 being mainly the rendering thing.
>
>Best wishes,
>Lauris Kaplinski
>
>
>
>
>
>_______________________________________________
>Libart mailing list
>Libart@gnome.org
>http://mail.gnome.org/mailman/listinfo/libart
--
----------------------------------------------------------------------------
You've got a SmartFriend in Pennsylvania
----------------------------------------------------------------------------
Leonard Rosenthol Internet: leonardr@lazerware.com
America Online: MACgician
Web Site: <http://www.lazerware.com/>
FTP Site: <ftp://ftp.lazerware.com/>
PGP Fingerprint: C76E 0497 C459 182D 0C6B AB6B CA10 B4DF 8067 5E65
This archive was generated by hypermail 2b25 : Tue Feb 06 2001 - 11:06:59 CST