John Culleton wrote:
\pdfobjcompresslevel=0
or
\pdfminorversion=4
It turns out that the OP was using Acrobat 5, so it all fits together.
Does the same command work with plain pdftex?
It should, both commands are pdftex primitives.
Best wishes,
Taco
Recent texlive 2008 installed on Linux Slackware 12.0 system.
I have a file that I can process via texexec and which shows up fine
on my Acrobat Reader, kpdf or xpdf. However another person using
(probably) Windows keeps getting corrupt file errors when he tries
to read it. And when I try
On Fri, Sep 26, 2008 at 8:00 PM, John Culleton [EMAIL PROTECTED]wrote:
Recent texlive 2008 installed on Linux Slackware 12.0 system.
I have a file that I can process via texexec and which shows up fine
on my Acrobat Reader, kpdf or xpdf. However another person using
(probably) Windows keeps
On Friday 26 September 2008 02:45:14 pm luigi scarso wrote:
maybe gs is too old.
you can try with 8.61 or 8.62 or 8.63 (and cross the fingers ...)
I downloaded ghostscript 8.63 but the pdf2ps error persists. but the
error goes away if I uses an earlier version of context, namely:
TeXExec
On Fri, Sep 26, 2008 at 11:29 PM, John Culleton [EMAIL PROTECTED]wrote:
On Friday 26 September 2008 02:45:14 pm luigi scarso wrote:
maybe gs is too old.
you can try with 8.61 or 8.62 or 8.63 (and cross the fingers ...)
I downloaded ghostscript 8.63 but the pdf2ps error persists. but
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been using,
and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new
context documents with
\pdfobjcompresslevel=0
or
On Fri, Sep 26, 2008 at 11:53 PM, Taco Hoekwater [EMAIL PROTECTED] wrote:
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been using,
and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new
context
On Friday 26 September 2008 05:53:59 pm Taco Hoekwater wrote:
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been
using, and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new
context documents
On Friday 26 September 2008 07:10:17 pm John Culleton wrote:
On Friday 26 September 2008 05:53:59 pm Taco Hoekwater wrote:
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been
using, and not in ghostscript nor in my code.
I am fairly certain
