Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <4226EA66.30203@freemail.hu>
Date: Thu, 03 Mar 2005 11:43:50 +0100
From: Bertalan Fodor <fodber AT freemail DOT hu>
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: ghostscript/fontconfig issues
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IIT-MailScanner-Information: Please contact the sysman AT iit DOT bme DOT hu for more information
X-MailScanner: Found to be clean
X-MailScanner-From: fodber AT freemail DOT hu
X-IsSubscribed: yes

Hello,

I've found the following bugs/issues about the ghostscript and 
fontconfig packages and their cooperation:
- fontconfig segfaults with old fonts in ghostscript (hr*), because they 
are buggy. AFAIK other ghostscript distributions do not contain them for 
the same reason.
- fontconfig's /etc/fonts/local.conf should contain the <dir> tag for 
/usr/share/ghostscript/fonts, to enable fontconfig-aware applications to 
use them. So gs and font-config should play together.

I think these two issues are to be solved by the maintainers of 
fontconfig and ghostscript.

Thank you,

Bert

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/