Bug 233194

Summary:	xine-lib not compiled with Freetype support
Product:	[Fedora] Fedora	Reporter:	Bastien Nocera <bnocera>
Component:	xine-lib	Assignee:	Aurelien Bompard <gauret>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	ville.skytta
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-03-22 06:46:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bastien Nocera 2007-03-20 20:22:39 UTC

This means that xine-lib can't load fonts listed in Fontconfig (such as the
user's Truetype fonts).

You'll probably want to include 2 of the patches at:
http://xine.cvs.sourceforge.net/xine/xine-lib/src/xine-engine/osd.c?view=log
Revision 1.85 and 1.86

http://xine.cvs.sourceforge.net/xine/xine-lib/src/xine-engine/osd.c?r1=1.84&r2=1.85
http://xine.cvs.sourceforge.net/xine/xine-lib/src/xine-engine/osd.c?r1=1.85&r2=1.86

Comment 1 Ville Skyttä 2007-03-20 22:52:42 UTC

After playing with a bit with various combinations of --with-freetype,
--with-fontconfig and --enable-antialiasing, my humble opinion is that these
options are not ready for prime time (and I guess upstream agrees as none of
them are enabled by default).  I couldn't find a font with which I could get
even acceptably readable subtitles, let alone better looking ones than the
non-freetype ones.  Enabling freetype/fontconfig seems to also screw xine-lib so
that the regular non-freetype fonts that come with it can no longer be selected.

The results I got with freetype/fontconfig looked somewhat like as in
http://farragut.flameeyes.is-a-geek.org/articles/2006/9 , but even less pretty.

I still have the updated package in my working dir and can commit it (making
ft/fontconfig build time optional, disabled by default) if there is demand. 
Aurelien, thoughts?

Comment 2 Aurelien Bompard 2007-03-22 06:46:59 UTC

I'd vote for staying as close to upstream as possible. If they think it's not
ready to be enabled by default, let's just wait till it's done.

Comment 3 Ville Skyttä 2007-03-26 19:58:01 UTC

Since I had the changes around already, I added the --with freetype and --with
antialiasing (both disabled by default) build time flags in 1.1.4-4 in devel.