<subject: postscript printing directs output to wrong directory. >
2007.05.24.14:06:21 UT
Hello octplot guys,
My system is a Dell OptiPlex GX260 (2400 MHz)
with an Intel 82845G/GL/GE/PE/GV graphics card. I have
WinXP SP2 with CygWin 1.5.24-2 that includes octave-2.1.73
as well as octave-forge and octave-headers. I'm using
the svn-470 and compiling with gcc-3.3.3-3.
The new svn-470 configures, compiles and installs O.K.
on my cygwin system, but printing with the '-dps' or '-deps'
options places the output file in the working directory
from which the octave session was started; not the current
working directory. The print utility with option '-djpg'
places output files in the current working directory.
I thought that this might be something that has come
up in recent revisions, but that is not so. I went to
svn440, and this occurs at least that far back.
This is very minor, but it is a potentially irritating
behavior. It may be impossible for octplot programmers to
address, because it's likely to be a problem with the
postscript rendering engine.
George
gbarrick@kent.edu
P.S. I found this when looking at .eps and .jpg outputs
from the text_demo.m script in svn463 as compared to
svn470. I was wanting to confirm for Shai some
improvement in the font rendering. I do not think that
I can see any difference in the font rendering from the
newer revisions, though I am rather a poorly trained judge
of fonts. Is there a font group (or another demo) for
which an improvement might be more visible?
Logged In: YES
user_id=136223
Originator: NO
fixed in svn 471
I suppose you being the first to report this very old bug means that no-one is producing ps/eps images with octplot. That's sad -- one of my goals was to create very good ps/eps output ...
Shai
Logged In: YES
user_id=136223
Originator: NO
fixed in svn 471
I suppose you being the first to report this very old bug means that no-one is producing ps/eps images with octplot. That's sad -- one of my goals was to create very good ps/eps output ...
Shai