print.m

[Ben Abbott]

On Apr 29, 2009, at 1:01 AM, Michael D. Godfrey wrote:

>> Attached is a test script that will produce various output files.  
>> This should run without errors on both Windows and Unix systems.
>
> Attached is what I got.  This may, in part, be due to using gnuplot  
> 4.2.3.
> I have seen errors like this before due to some timing problem in the
> communication with gnuplot.
>
> But, 4.2.3 is the current official version with Fedora 10, so it  
> would be
> good if it worked correctly.
>
> The plots looked OK.
>
> And, other plots of my current stuff were OK, too.  No errors.
>
> Michael
>
>> octave:1> test_print
>>
>> multiplot> et origin 0, 0
>>           ^
>>           line 0: invalid command
>>
>>
>> multiplot> et origin 0, 0
>>           ^
>>           line 0: invalid command
>>
>> gdImageStringFT: Could not find/open font while printing string  
>> figure size is 8x6 inches with font
>> gdImageStringFT: Could not find/open font while printing string 2  
>> with font
>> gdImageStringFT: Could not find/open font while printing string  
>> figure size is 8x6 inches with font
>> gdImageStringFT: Could not find/open font while printing string 2  
>> with font
>> gdImageStringFT: Could not find/open font while printing string  
>> figure size is 8x6 inches with font
>> gdImageStringFT: Could not find/open font while printing string 2  
>> with font
>> gdImageStringFT: Could not find/open font while printing string  
>> figure size is 8x6 inches with font
>> gdImageStringFT: Could not find/open font while printing string 2  
>> with font
>> gdImageStringFT: Could not find/open font while printing string  
>> figure size is 8x6 inches with font
>> gdImageStringFT: Could not find/open font while printing string 2  
>> with font
>> gdImageStringFT: Could not find/open font while printing string  
>> figure size is 8x6 inches with font
>> gdImageStringFT: Could not find/open font while printing string 2  
>> with font
>>
>

Michael, is this reproducible for you?

When I encounter such a problem, it goes away when I restart  
Octave ... which is a problem, not a solution.

If you can reproduce this, perhaps it will be possible to find a  
solution.

Ben