-->Ok, so my hard drive had a failure last night. Here I was, in the >middle of writing SVG parsing stuff, and the power flickers, and when >I was booting my machine, the drive won't spin up any more. Arggh. >So, after I came to grips with the data loss, and the facts that I >should really have a UPS and do backups more often, I realized that >all of the Linux distributions I have around are pretty ancient. > >So, while I was picking up a new hard drive at Fry's this morning, I >decided to grab a copy of Red Hat 6.0 while I was at it. Cool, so >I've got everything up and running again, but once I tried to build >AbiWord from CVS, I came across that 'Can't find helvetica' problem >that everyone's been complaining about. So, I looked through the >code, and found that it wants it only for the GUI stuff, not the body >of some document, and that xap_UnixFontXLFD is being very particular >about what font it wants. So, I quickly added a work-around by adding >a getFallbackXLFD to that class which only specifies the family, >weight, slant and point size. I also changed xap_UnixFont to use the >fallback font if it can't get the exact font it wants. > >Great -- everyone works for me now. But, I wonder if this is a good >solution or not. xap_UnixFontXLFD is actually specifying '0' for >things like resX and resY in the non-fallback font, and Red Hat 6.0's >custom font server can't cope with this. Is AbiWord in error by doing >this? Shaw? > >-- >Matt Kimball >mkimball@xmission.com
Eric W. Sink, Software Craftsman eric@abisource.com