[Bf-committers] Possible fix for bug #1483 (Internat. font path badly constructed)

[Wouter van Heyst]

On Fri, Aug 06, 2004 at 02:38:03PM +0200, Stefan Gartner wrote:
> On Friday 06 August 2004 12:57, Wouter van Heyst wrote:
> > On Fri, Aug 06, 2004 at 11:29:21AM +0200, Stefan Gartner wrote:
> > > Hi all,
> > > the attached patch should fix bug #1483, however I'm not quite sure if
> > > it's 100% correct. Especially the following questions remain:
> >
> > Does this leave the OSX bundle case intact?
> 
> The OSX bundle case is just a special case of the problem, IIRC if it couldn't 
> find the font specified, it tried to load the default font, which happened to 
> be inside the bundle on OSX. Or something like that.
> In other words: the modified code never touches any OSX-specific stuff, so if 
> it worked before, it should work now as well.

True, it just involves some more locations to try.

> >
> > > * is there a better way than using BLI_split_dirfile() to get the
> > > basename of a file?
> > > * Why is the full path to the font file stored in U.fontname?
> >
> > Huu, a relative path might make sense, but an absolute one?
> 
> relative to what?

Relative to the fondir, ie:
	fontdir = /usr/local/share/fonts
	fontname = iso646-1/efont.ttf

Wouter