Bug 688705 - Fontconfig support for ghostscript
Summary: Fontconfig support for ghostscript
Status: RESOLVED DUPLICATE of bug 687595
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Build Process (show other bugs)
Version: 0.00
Hardware: PC Linux
: P4 enhancement
Assignee: Ralph Giles
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-17 11:47 UTC by Stefan Schweizer
Modified: 2007-12-13 12:55 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments
ghostscript-esp-fontconfig.patch (7.23 KB, patch)
2006-05-17 11:48 UTC, Stefan Schweizer
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Schweizer 2006-05-17 11:47:52 UTC
This patch adds fontconfig support for ghostscript if fontconfig is available.
Comment 1 Stefan Schweizer 2006-05-17 11:48:39 UTC
Created attachment 2206 [details]
ghostscript-esp-fontconfig.patch

had a minor problem with applying for me but is really easy to fix.
Comment 2 Ralph Giles 2006-05-19 07:54:02 UTC
Is this a newer version of the patch from bug #687595?

Note that we can't just apply large patches from ESP Ghostscript because of the
license conflict; we need permission and assignment from the author.

In any case, we definitely want to support fontconfig when it's available. We
already have stubs for native font enumeration systems, but I think they're only
implemented on MacOS Carbon.
Comment 3 Stefan Schweizer 2006-09-01 09:14:29 UTC

*** This bug has been marked as a duplicate of 687595 ***
Comment 4 Craig Ringer 2006-09-20 07:30:00 UTC
I originally wrote the core of the attached patch (and take full blame for any
errors that lie therein - I was pretty new to plain C at the time). My
unmodified version can be found on the Scribus bug tracker link in #67595. My
patch was always intended for inclusion in mainline gs, and I'd be very happy to
take care of any required copyright assignments to make that possible.

By the looks there haven't been serious changes to the actual code, though the
all -important build integration has been done (thanks!). I would personally
expect it to be fine to merge as-is.