Issue 8144 - Fontconfig2 based systems (RH8) store fonts in /usr/share/fonts - OOo doesn't look there...
Summary: Fontconfig2 based systems (RH8) store fonts in /usr/share/fonts - OOo doesn't...
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 643
Hardware: PC Linux, all
: P3 Trivial with 4 votes (vote)
Target Milestone: OOo 2.0
Assignee: ulf.stroehler
QA Contact: issues@gsl
URL:
Keywords:
: 2728 28242 (view as issue list)
Depends on:
Blocks: 20361
  Show dependency tree
 
Reported: 2002-10-08 09:12 UTC by mdekkers
Modified: 2004-12-06 08:40 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mdekkers 2002-10-08 09:12:32 UTC
Hi, 
 
Fontconfig2 based systems, like RedHat8, store ttf's in /usr/share/fonts, 
rather then the old XFree location. OOo 643, and possible older versions, 
don't look there for fonts, hence new fonts don't show up.
Comment 1 mdekkers 2002-10-08 09:27:33 UTC
Chris Halls rightly suggest to change this from "change hardcoded 
paths" to "support fontconfig2" 
Comment 2 christof.pintaske 2002-10-08 15:19:10 UTC
CP->PL: supporting fontconfig2 is probably the right thing to do.
Maybe not for 1.1. Please have a look if we can support /usr/share/fonts. 
Comment 3 philipp.lohmann 2002-10-09 10:37:23 UTC
will do
Comment 4 mlei 2002-11-04 00:27:42 UTC
Is the long-term plan to use fontconfig in OOo, replacing the current
OOo font mechanism?

The interim solution should not be to look in a hardcoded location
such as /usr/share/fonts, but to peek in the /etc/fonts/fonts.conf
file and pull the directories from the list there.
Comment 5 philipp.lohmann 2002-11-04 09:34:49 UTC
If fontconfig does not have an API to access the font files, then i
will have to do that.
Comment 6 mlei 2002-11-04 13:30:35 UTC
Fontconfig does have the API to access the font files, iirc. I only
suggested that interim solution in the case that using the fontconfig
api (and thus pulling in a library) wasn't feasible yet.

Philipp, are you (will you be) working on integrating fontconfig into OOo?
Comment 7 philipp.lohmann 2002-11-04 13:39:11 UTC
I will. I haven't got anything material yet (workload), but i plan to
open the libXft by dlopen and use it if possible, else fall back to
what is already there.
Comment 8 jvromans 2002-11-22 11:15:55 UTC
Please be careful. Many font related problems I find are related to
OOo getting fonts from all over the place. Not all fonts that are
installed as part of the system are equally useful.
In any case, there should be a (customizable) way to control the
locations where OOo looks for fonts.
Comment 9 mlei 2002-11-22 20:02:49 UTC
If and when we do start using fontconfig by default, that should
become a moot point, as fontconfig's purpose is to make sure every
font that is used is both displayable and printable.

I agree, though, that we should not be just looking in the default
font directories for any fonts that might be there. I would suggest
that this bug's summary be changed to "Support fontconfig"
Comment 10 philipp.lohmann 2003-01-23 18:19:52 UTC
*** Issue 2728 has been marked as a duplicate of this issue. ***
Comment 11 mlei 2003-04-03 01:47:15 UTC
Ximian has been working on some code for fontconfig integration that
they are planning to contribute back to OOo at some point. Philipp (or
others), would it be possible to contact someone at Ximian to try to
get some initial patches posted and reviewed?
Comment 12 philipp.lohmann 2003-04-03 14:34:37 UTC
Michael Meeks told me Ximian would do so when they are ready. But we'd
need to change that anyway since they simply linked against libXft2.so
which cannot be a solution for OOo as a whole; we'll want that as a
runtime decision.
Comment 13 mmeeks 2003-04-07 09:15:39 UTC
We don't link to Xft2, we link to libfontconfig, from which we extract
a list of fonts to use - which we use in the normal way - so far.
Clearly it'd be nice to use Xft2 / fontconfig more fully - but that
creates issues. Either way; AFAICS Xft2 use is a different issue to
fontconfig use.
Comment 14 philipp.lohmann 2003-04-07 09:43:50 UTC
You're right. Nevertheless the same line of reasoning is valid for
libfontconfig; I'd like to link it dynamically.
Comment 15 philipp.lohmann 2003-09-05 14:22:40 UTC
fixed in CWS fontconfig
Comment 16 ulf.stroehler 2003-09-24 09:22:34 UTC
*** Issue 19500 has been marked as a duplicate of this issue. ***
Comment 17 philipp.lohmann 2003-10-17 11:48:22 UTC
pl->us: please verify in CWS fontconfig
Comment 18 nospam4obr 2004-02-06 14:21:03 UTC
#20361# is the corresponding Q-PCD issue for fontconfig support.
Comment 19 ulf.stroehler 2004-06-04 10:17:59 UTC
Issue is resolved/fixed.
Comment 20 ulf.stroehler 2004-06-04 10:18:26 UTC
Issue verified.
Comment 21 ulf.stroehler 2004-06-04 10:19:03 UTC
Closing resolved/fixed/verified.
Comment 22 ulf.stroehler 2004-12-06 08:40:32 UTC
*** Issue 28242 has been marked as a duplicate of this issue. ***