[17752] in Athena Bugs
sun4 8.3.27: distill
daemon@ATHENA.MIT.EDU (Sara C Pickett)
Wed Apr 12 15:38:55 2000
Message-Id: <200004121938.PAA22161@m56-129-17.mit.edu>
To: bugs@MIT.EDU
Date: Wed, 12 Apr 2000 15:38:46 -0400
From: Sara C Pickett <sarac@MIT.EDU>
System name: m56-129-17.mit.edu
Type and version: Ultra-5_10 8.3.27
Display type: m
Shell: /bin/athena/tcsh
Window manager: mwm
What were you trying to do?
Distill a document to pdf, using distill in the acro
locker.
What's wrong:
Every single time I run it, it prints the message:
Using user-customized resource file...
WARNING: This version of the Acrobat Distiller may not be fully
compatible with previous versions of Acrobat Exchange
and Acrobat Reader due to new functionality based on
recent PDF language additions. To ensure compatibility
with previous versions of Acrobat Exchange and Acrobat
Reader, the DEFAULT for compatibility can be set inside
your personal preference file. Setting this compatibility
switch, however, will result in the disabling of new
features of the Acrobat Distiller. The compatibility
switch may easily be overridden at run-time through the
specification of -compatlevel and in no way represents an
actual permanent loss of features for Acrobat Distiller.
NOTE: Running the Acrobat Distiller with the -noprefs option
will effectively disable the preference chosen below.
Enter Acrobat Distiller personal preferences file modification [1, 2, 3]
[1] use 3.0 new features
[2] use 2.1 compatibility
[3] leave compatibility undefined
I always choose 2, for the 2.1 compatibility. However, despite what
it says in the message, it asks me to pick the compatibility level
every time.
"distill -params" shows that -compatlevel is set to 2.1, so it looks
like it does save that information, but ignores it. Sigh.
When I explicitly ran
distill -compatlevel 2.1 filename.ps
it still asks me. For that matter, when I run it with
"-compatlevel 3.0", it still asks me to pick a compatibility level.
Argh.
I tried moving my ~/.acrorc and ~/.acrosrch files elsewhere, in hopes
that that would take care of the problem, but it didn't.
What should have happened:
It should only ever ask me about compatibility once, and not
every single time I've run it for the past 2 years! :-P (This isn't
a new problem, I just hadn't gotten around to reporting it before now.)
Please describe any relevant documentation references:
[Please replace this line with your information.]
