[Scribus] Scribus for Mac OS X

[Michael Crisci]

Well,

    I ran Scribus until it quit by itself. I looked into the activity  
monitor, and I saw Scribus was looking for fonts like it should, but  
I do have two very large hard drives on the computer (120G and 280G).  
Could this be holding up the process to the point that it just quits?  
Is there any way to direct Scribus to just go to one spot to get the  
fonts?

Michael Crisci

If you think dogs can't count, try putting three dog
biscuits in your pocket and then give him only two of them.
- Phil Pastoret


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://nashi.altmuehlnet.de/pipermail/scribus/attachments/20070123/bf5b3592/attachment-0001.html