On Jul 14, 2008, at 8:43 AM, Martin Costabel wrote:
> Stan Sanderson wrote:
> []
>> I rebuilt freetype219 with no change in qtconfig results.
>
> I have no evidence for assuming that freetype is involved in this
> problem; I just try to find out what is different on your machine.
>
> As for fon
Stan Sanderson wrote:
[]
>
> I rebuilt freetype219 with no change in qtconfig results.
I have no evidence for assuming that freetype is involved in this
problem; I just try to find out what is different on your machine.
As for font caches that might need purging, the obvious ones are in
/usr/X
On Jul 14, 2008, at 4:17 AM, Martin Costabel wrote:
> Stan Sanderson wrote:
>> On Jul 13, 2008, at 3:34 PM, Martin Costabel wrote:
>>> Stan Sanderson wrote:
>>> []
Well, it seems odd that "lsof | grep qtconfig" returns nothing.
>>> Perhaps a misunderstanding: It only returns anything while q
Stan Sanderson wrote:
>
> On Jul 13, 2008, at 3:34 PM, Martin Costabel wrote:
>
>> Stan Sanderson wrote:
>> []
>>> Well, it seems odd that "lsof | grep qtconfig" returns nothing.
>> Perhaps a misunderstanding: It only returns anything while qtconfig
>> is running.
>>
>
> Additional- a picture of
On Jul 13, 2008, at 3:34 PM, Martin Costabel wrote:
> Stan Sanderson wrote:
> []
>> Well, it seems odd that "lsof | grep qtconfig" returns nothing.
>
> Perhaps a misunderstanding: It only returns anything while qtconfig
> is running.
>
Additional- a picture of the qtconfig window is also at the
On Jul 13, 2008, at 3:34 PM, Martin Costabel wrote:
> Stan Sanderson wrote:
> []
>> Well, it seems odd that "lsof | grep qtconfig" returns nothing.
>
> Perhaps a misunderstanding: It only returns anything while qtconfig
> is running.
>
> --
> Martin
>
>
Martin-
"Perhaps" is very kind. No, I
Stan Sanderson wrote:
[]
> Well, it seems odd that "lsof | grep qtconfig" returns nothing.
Perhaps a misunderstanding: It only returns anything while qtconfig is
running.
--
Martin
-
Sponsored by: SourceForge.net Communi
On Jul 13, 2008, at 2:22 PM, Martin Costabel wrote:
> Stan Sanderson wrote:
> []
>> 1. qtconfig produced a window with no readable text, only squiggles.
>
> At least this shows that the problem lies with qt3, not with
> scribus. Once you get qtconfig working, I am confident scribus will
> wor
Stan Sanderson wrote:
[]
> 1. qtconfig produced a window with no readable text, only squiggles.
At least this shows that the problem lies with qt3, not with scribus.
Once you get qtconfig working, I am confident scribus will work, too.
Have you tried to remove ~/.qt/? And run fc-cache?
Otherwi
On Jul 13, 2008, at 1:18 AM, Martin Costabel wrote:
Stan Sanderson wrote:
[]
I spoke too soon. Scribus is at about 85%. Text in some of the
dialogue boxes, especially those related to text selection, is
still missing. For example, under Preferences->Tools, the Font
selection drop-down
Stan Sanderson wrote:
[]
> I spoke too soon. Scribus is at about 85%. Text in some of the
> dialogue boxes, especially those related to text selection, is still
> missing. For example, under Preferences->Tools, the Font selection
> drop-down box has the ]ps symbol followed by mostly empty spa
On Jul 12, 2008, at 2:42 PM, Stan Sanderson wrote:
>
> On Jul 12, 2008, at 1:42 AM, Martin Costabel wrote:
>
>> Stan Sanderson wrote:
>> []
>>> OK- I have rebuilt qt3 with no change in the results. qtconfig
>>> returns
>>> the same squiggly noise-type tiny symbols on the panels. Now
>>> what...
On Jul 12, 2008, at 1:42 AM, Martin Costabel wrote:
> Stan Sanderson wrote:
> []
>> OK- I have rebuilt qt3 with no change in the results. qtconfig
>> returns
>> the same squiggly noise-type tiny symbols on the panels. Now what...?
>
> One thing to check is the permissions on the directory ~/.qt
Stan Sanderson wrote:
[]
> OK- I have rebuilt qt3 with no change in the results. qtconfig returns
> the same squiggly noise-type tiny symbols on the panels. Now what...?
One thing to check is the permissions on the directory ~/.qt. If it's
not writable by you, it can cause font problems.
--
M
On Fri, Jul 11, 2008 at 09:55:41PM -0500, Stan Sanderson wrote:
>
> On Jul 11, 2008, at 5:15 PM, Martin Costabel wrote:
>
> > Stan Sanderson wrote:
> >> Scribus134 installed without a problem on my PPC, 10.5.4, running
> >> xquartx 2.2.3.
> >> However, when the Scribus window(s) appears, no le
On Jul 11, 2008, at 9:55 PM, Stan Sanderson wrote:
>
> On Jul 11, 2008, at 5:15 PM, Martin Costabel wrote:
>
>> Stan Sanderson wrote:
>>> Scribus134 installed without a problem on my PPC, 10.5.4, running
>>> xquartx 2.2.3.
>>> However, when the Scribus window(s) appears, no legible text is
>>> vi
On Jul 11, 2008, at 5:15 PM, Martin Costabel wrote:
> Stan Sanderson wrote:
>> Scribus134 installed without a problem on my PPC, 10.5.4, running
>> xquartx 2.2.3.
>> However, when the Scribus window(s) appears, no legible text is
>> visible. Some squiggles are present, but are not legible e
Stan Sanderson wrote:
> Scribus134 installed without a problem on my PPC, 10.5.4, running
> xquartx 2.2.3.
>
> However, when the Scribus window(s) appears, no legible text is
> visible. Some squiggles are present, but are not legible enough to
> determine if they are noise or from a particul
On Jul 11, 2008, at 12:02 PM, Alexander Hansen wrote:
> On Friday 11 July 2008 11:58:19 Stan Sanderson wrote:
>> Scribus134 installed without a problem on my PPC, 10.5.4, running
>> xquartx 2.2.3.
>>
>> However, when the Scribus window(s) appears, no legible text is
>> visible. Some squiggles are
On Friday 11 July 2008 11:58:19 Stan Sanderson wrote:
> Scribus134 installed without a problem on my PPC, 10.5.4, running
> xquartx 2.2.3.
>
> However, when the Scribus window(s) appears, no legible text is
> visible. Some squiggles are present, but are not legible enough to
> determine if they are
Scribus134 installed without a problem on my PPC, 10.5.4, running
xquartx 2.2.3.
However, when the Scribus window(s) appears, no legible text is
visible. Some squiggles are present, but are not legible enough to
determine if they are noise or from a particular font.
I have moved the ~/.scri
21 matches
Mail list logo
