Hi Darren,
Thanks for your reply. I am sending you a postscript figure from my
upcoming Astrophysical Journal paper and the barebones Python/Pylab code
used to generate it.
I do not normally use the psdistiller or usetex options. I have changed
my rc settings by letting numerix = numarray. Otherwise, they are the
same as the default in all fields.
I am using matplotlib CVS (current as of yesterday). My operating system
is Debian "testing," which by default uses Python 2.3 (not 2.4). I always
just use Python 2.3 per the Debian default. The packages are current.
For the paper itself, I use Latex2e (AASTEX just has Latex macros to
help typeset papers for ApJ). But the problem shows up when I do ps2pdf
on the fig.ps file as well as ps2pdf on the whole paper. So I don't think
that's the issue.
I'm using GPL (not Aladdin) Ghostscript for the ps2pdf. Although fig.pdf
displays correctly in acroread and xpdf, it does not print correctly (when
I go print... in acroread 7). Using epstopdf produces the same thing: an
apparently fine pdf file of the figure that doesn't print properly.
Thanks,
Curtis
T_formula.py (1.37 KB)
fig.ps (268 KB)
fig.pdf (14.3 KB)
Hi Darren,
Thanks for your reply. I am sending you a postscript figure from my
upcoming Astrophysical Journal paper and the barebones Python/Pylab code
used to generate it.
I do not normally use the psdistiller or usetex options. I have changed
my rc settings by letting numerix = numarray. Otherwise, they are the
same as the default in all fields.
I am using matplotlib CVS (current as of yesterday). My operating system
is Debian "testing," which by default uses Python 2.3 (not 2.4). I always
just use Python 2.3 per the Debian default. The packages are current.
For the paper itself, I use Latex2e (AASTEX just has Latex macros to
help typeset papers for ApJ). But the problem shows up when I do ps2pdf
on the fig.ps file as well as ps2pdf on the whole paper. So I don't think
that's the issue.
I'm using GPL (not Aladdin) Ghostscript for the ps2pdf. Although fig.pdf
displays correctly in acroread and xpdf, it does not print correctly (when
I go print... in acroread 7). Using epstopdf produces the same thing: an
apparently fine pdf file of the figure that doesn't print properly.
What OS are you using? I just printed your pdf file from kpdf on a RHEL4
machine, and it looks fine.
What OS are you using? I just printed your pdf file from kpdf on a RHEL4
machine, and it looks fine.
I'm using the "testing" distribution of Debian Linux, i386 architecture.
I'm using version 0.3.9 of GNU ghostscript and acroread 7.0.0 dated
03/11/2005 (C) Adobe Systems.
Hi Curtis,
I'm afraid I can't be of much help. I've printed your pdf files on two
different computers now, one at work and one at home, without any problems.
Maybe you have a problem with your printer driver?
Darren
···
On Tuesday 31 January 2006 2:55 pm, Curtis Cooper wrote:
Hi Darren,
Thanks for your reply. I am sending you a postscript figure from my
upcoming Astrophysical Journal paper and the barebones Python/Pylab code
used to generate it.
I do not normally use the psdistiller or usetex options. I have changed
my rc settings by letting numerix = numarray. Otherwise, they are the
same as the default in all fields.
I am using matplotlib CVS (current as of yesterday). My operating system
is Debian "testing," which by default uses Python 2.3 (not 2.4). I always
just use Python 2.3 per the Debian default. The packages are current.
For the paper itself, I use Latex2e (AASTEX just has Latex macros to
help typeset papers for ApJ). But the problem shows up when I do ps2pdf
on the fig.ps file as well as ps2pdf on the whole paper. So I don't think
that's the issue.
I'm using GPL (not Aladdin) Ghostscript for the ps2pdf. Although fig.pdf
displays correctly in acroread and xpdf, it does not print correctly (when
I go print... in acroread 7). Using epstopdf produces the same thing: an
apparently fine pdf file of the figure that doesn't print properly.
Thanks,
Curtis
--
Darren S. Dale, Ph.D.
dd55@...163...
Thanks for the feedback! It sounds like it's just a quirk of my
particular setup and will not inhibit usage of the figures in the paper.
So, I'll ignore it, since I can always print it perfectly from just the
postscript directly.
Cheers,
Curtis
* * * * * * * * * * * * * * * * * * * * * * * * * * * *
* Curtis S. Cooper, Graduate Research Assistant *
* Lunar and Planetary Laboratory, University of Arizona *
* http://www.lpl.arizona.edu/~curtis/ *
* Kuiper Space Sciences, Rm. 318 *
* 1629 E. University Blvd., *
* Tucson, AZ 85721 * * * * * * * * * * * * * * *
* Wk: (520) 621-1471 *
* * * * * * * * * * * *
···
On Thu, 2 Feb 2006, Darren Dale wrote:
Hi Curtis,
I'm afraid I can't be of much help. I've printed your pdf files on two
different computers now, one at work and one at home, without any problems.
Maybe you have a problem with your printer driver?
Darren
On Tuesday 31 January 2006 2:55 pm, Curtis Cooper wrote:
> Hi Darren,
>
> Thanks for your reply. I am sending you a postscript figure from my
> upcoming Astrophysical Journal paper and the barebones Python/Pylab code
> used to generate it.
>
> I do not normally use the psdistiller or usetex options. I have changed
> my rc settings by letting numerix = numarray. Otherwise, they are the
> same as the default in all fields.
>
> I am using matplotlib CVS (current as of yesterday). My operating system
> is Debian "testing," which by default uses Python 2.3 (not 2.4). I always
> just use Python 2.3 per the Debian default. The packages are current.
>
> For the paper itself, I use Latex2e (AASTEX just has Latex macros to
> help typeset papers for ApJ). But the problem shows up when I do ps2pdf
> on the fig.ps file as well as ps2pdf on the whole paper. So I don't think
> that's the issue.
>
> I'm using GPL (not Aladdin) Ghostscript for the ps2pdf. Although fig.pdf
> displays correctly in acroread and xpdf, it does not print correctly (when
> I go print... in acroread 7). Using epstopdf produces the same thing: an
> apparently fine pdf file of the figure that doesn't print properly.
>
> Thanks,
> Curtis
--
Darren S. Dale, Ph.D.
dd55@...163...
Darren,
Your suggestion to use afm fonts worked! It results in nice, small file
sizes and fixes the ps2pdf problem I was having.
Thanks,
Curtis