Hi Michael, there is a file "checkfonts.xml" path: ~/.scribus/checkfonts.xml
You can try to delete this (it's a collection of cached font paths) or delete the whole .scribus folder. It will be recreated after you start scribus. You might want to backup the whole thing before, though - if you delete the whole folder, your prefs and colors (and?) will also be lost. cheers Jon Am 24.01.2007 um 00:04 schrieb Michael Crisci: > I let it run as long as it wanted, and it then just quit. > > > Michael Crisci > > > "You have your friends, the telephone, your computer, your TV and your > job. Your dog only has you..." > > Paul Harvey > > > > On Jan 22, 2007, at 7:43 AM, avox wrote: > >> >> >> >> Michael Crisci wrote: >>> >>> Craig, >>> >>> ? Yesterday I left Scribus running for over a half an hour, and it >>> was still stalled on setting up the font cache. Should it take that >>> long? I suspect something else may be the cause. Is there anyone I >>> can contact to do a diagnostic check and walk-through on this >>> program? >>> >> >> Building the font cache the first time might well take half an hour. >> Difficult to tell since it depends on the number of fonts you have and >> your hardware. But I'd not expect more than two hours on a PPC. >> >> About installing/deinstalling: >> >> The 1337 binary is self-contained and doesn't use any of the old >> libraries, except Ghostscript. Removing the Scribus.app bundle will >> uninstall. >> There are also some Scribus settings in /Users/yourname/.scribus . >> This is a hidden directory, but it doesn't take much space and you >> can ignore it. If you need to remove it you can do it from the >> Terminal application with "cd ; rm -rf .scribus" (take care you dont >> add any spaces within ".scribus" !) >> >> If you want to check what Scribus is doing, there are two >> possibilities: >> a) open /Applications/Utilities/Console.app and search for any output >> Scribus makes >> b) open Activity Monitor, select the Scribus process, and click on the >> information icon (blue 'i'), then on analyze. This gives you a list of >> functions Scribus spent time in recently. >> >> It's also possible to start Scribus in debug mode from the Terminal: >> just type "gdb /Applications/Scribus.app" and Enter. In this case >> all Scribus messages are written to the Terminal instead of the >> Console >> and you can interrupt Scribus at any time by pressing Ctrl-C in the >> Terminal and set breakpoints, print backtraces etc. >> >> /Andreas >> -- >> View this message in context: >> http://www.nabble.com/Re%3A--Scribus--Scribus-for-Mac-OS-X- >> tf3034157.html#a8495898 >> Sent from the Scribus mailing list archive at Nabble.com. >> >> _______________________________________________ >> Scribus mailing list >> Scribus at nashi.altmuehlnet.de >> http://nashi.altmuehlnet.de/mailman/listinfo/scribus > _______________________________________________ > Scribus mailing list > Scribus at nashi.altmuehlnet.de > http://nashi.altmuehlnet.de/mailman/listinfo/scribus
