Bug 4064

Summary:	fontconfig gives bad matches for default fonts
Product:	poppler	Reporter:	Jeff Muizelaar <jmuizelaar>
Component:	general	Assignee:	Kristian Høgsberg <krh>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	high	CC:	m_kretzschmar
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Jeff Muizelaar 2005-08-13 08:52:46 UTC

If the x fonts from packages like xfonts-75dpi are installed then fontconfig
will suggest fonts like helvB10.pcf.gz which match the family name of
"Helvetica" perfectly. However, these fonts are completely unsuitable for use in
pdfs.

Comment 1 Martin Kretzschmar 2005-08-19 10:57:17 UTC

Is that with the new fontconfig code?

I changed the old fontconfig code a thousand times to get workaround this problem.

Comment 2 Jeff Muizelaar 2005-09-04 21:09:19 UTC

It was with the new fontconfig code

Comment 3 Albert Astals Cid 2005-10-23 05:32:21 UTC

Well, IMHO that's a problem with your fontconfig configuration, you should do 
something like  
 
<match target="pattern"> 
    <test name="prefer_outline"> 
        <bool>true</bool> 
    </test> 
    <test name="family"> 
        <string>Helvetica</string> 
    </test> 
    <edit name="family" mode="prepend" binding="same"> 
        <string>Nimbus Sans L</string> 
    </edit> 
</match> 
 
That is, fontconfig can not do magic, you should help it. 
BTW Mandriva is already doing that in their default fontconfig configuration 
so bug your distribution to improve their fontconfig configuration. 
I think we should put in the wiki some/most/all of the rules needed for 
fontconfig so that it behaves like the old hardcoded way as a recommendation 
for distributions, what do you think?

Comment 4 Federico Fissore 2006-01-26 07:52:37 UTC

could this lead to error messages like

Error: Couldn't find a font for 'Times Roman'
some font thing failed
Error: Couldn't find a font for 'Times Italic'
some font thing failed
Error: Couldn't find a font for 'Times Bold'
some font thing failed 

given by evince? they even lead it to crash in the end

Comment 5 Wouter Bolsterlee 2006-02-08 02:05:43 UTC


*** This bug has been marked as a duplicate of 4030 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.