----- Forwarded message from [EMAIL PROTECTED] ----- To: Blue Lizard <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: Pango? References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> From: Havoc Pennington <[EMAIL PROTECTED]> Date: 25 Apr 2002 23:36:57 -0400 In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii
Blue Lizard <[EMAIL PROTECTED]> writes: > On Thu, 2002-04-25 at 02:46, Martin Sevior wrote: > > It contains a lot of what we need but not everything we need. Nor is it > > cross platform. > > This is an issue I have been thinking about a lot. The more abiword is > integrated into gnome/pango (or for that matter any other platform > specific thing) the more features get developed on that, and left out or > made different on other platforms. Like, if we use pango for kerning, > what does win32 do? qnx? solaris/cde users that dont want no stinking > gnome build? The options as I can figure them out are: a) Use platform-specific engines, Pango/Uniscribe/etc. b) Use one engine on all platforms So a) has the problem you described, and b) doesn't. If Pango is used as the engine in b) then there is no problem like the one you mention. If you go with a), then Pango isn't creating the problem you mention, the decision to go with a) is creating it. Havoc ----- End forwarded message -----
