PostScript - Re: analysing invalidfont problem?

Author

Re: analysing invalidfont problem?

bugbear

2006-06-24, 8:17 am

bugbear wrote:
>
> It appears to be related to the version of GS,
> since gs 7.07 (on linux) can handle it, but
> gs 8.14 (on solaris) can't.

OK; I tried to download, compile and install
gs8.54 to further isolate my font issue.

But I've run into an install-and-run
issue.

I used configure to set the install prefix to
my home directory, and did a make debug, make
install.

I also installed the fonts in the appropriate place.

I now get this message whenever I use a
device other than nulldevice.

Error: /invalidfileaccess in --.outputpage--

My command was:
~/bin/gs -sDEVICE=psgray -dBATCH -dNOPAUSE ./code/gs/ghostscript-8.54-gpl/examples/golfer.eps -sOutputFile=ooo

running strace, it appears to be trying (and failing) to find
a file called IdiomSet

Any and all advice welcomed

BugBear

bugbear

2006-06-24, 8:17 am

SaGS wrote:
> bugbear wrote:
>
>
>
> "trying (and failing) to find" as in "open file" or "find first file/
> find next file" (I'm not familiar with *nix)?

This kind of thing...

open("/home/bugbear/.fonts/IdiomSet", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECT
ORY) = -1 ENOENT (No such file or directory)
open("/home/bugbear/share/ghostscript/8.54/lib/IdiomSet", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECT
ORY) = -1 ENOENT (No such file or directory)
open("/home/bugbear/share/ghostscript/8.54/Resource/IdiomSet", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECT
ORY) = -1 ENOENT (No such file or directory)
open("/home/bugbear/share/ghostscript/fonts/IdiomSet", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECT
ORY) = -1 ENOENT (No such file or directory)
open("/home/bugbear/Resource/IdiomSet", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECT
ORY)

>
> Just a shot in the dark for the first case: do you have a "IdiomSet"
> DIRECTORY, especially somewhere in the directories where GS looks for
> resources?

I have neither directories nor files with that name
anywhere in my entire home tree.

Thanks for trying to help.

BugBear

Dan Coby

2006-06-24, 8:17 am

"bugbear" <bugbear@trim_papermule.co.uk_trim> wrote in message
news:449bc9f2$0$69359$ed2619ec@ptn-nntp-reader01.plus.net...
> bugbear wrote:

> My command was:
> ~/bin/gs -sDEVICE=psgray -dBATCH -dNOPAUSE
> ./code/gs/ghostscript-8.54-gpl/examples/golfer.eps -sOutputFile=ooo

You need to specify the output file before the input file. Ghostscript
generally processes
command line arguments in order along the command line. So with your command
line
Ghostscript is trying to process the input file before the output file has
been specified.

~/bin/gs -sDEVICE=psgray -dBATCH -dNOPAUSE -sOututFile=ooo
../code/gs/ghostscript-8.54-gpl/examples/golfer.eps

bugbear

2006-06-26, 4:15 am

Dan Coby wrote:
> "bugbear" <bugbear@trim_papermule.co.uk_trim> wrote in message
> news:449bc9f2$0$69359$ed2619ec@ptn-nntp-reader01.plus.net...
>
>
>
>
>
> You need to specify the output file before the input file. Ghostscript
> generally processes
> command line arguments in order along the command line. So with your command
> line
> Ghostscript is trying to process the input file before the output file has
> been specified.
>
> ~/bin/gs -sDEVICE=psgray -dBATCH -dNOPAUSE -sOututFile=ooo
> ./code/gs/ghostscript-8.54-gpl/examples/golfer.eps
>

Thanks for the tip; I made the change you propose;

ly
I had the same result:

~/bin/gs -sDEVICE=psgray -dBATCH -dNOPAUSE -sOututFile=ooo ./code/gs/ghostscript-8.54-gpl/examples/golfer.eps

GPL Ghostscript 8.54 (2006-05-17)
Copyright (C) 2006 artofcode LLC, Benicia, CA. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
GPL Ghostscript 8.54: **** Could not open the file .
Error: /invalidfileaccess in --.outputpage--

strace again shows (desperate) attempts to open a directory called
IdiomSet

BugBear

bugbear

2006-06-26, 8:02 am

SaGS wrote:
> bugbear wrote:
>
>
>
> This could be from GS searching the %GS_LIB% path for IdiomSet resource
> instances. It's normal during "bind", and the fact that it finds none
> should have no adverse consequence.
>
>
>
>
> "-sOututFile" should be "-sOutputFile", with a "p". If it's a typo in
> your real command, not only in your post, you still have no output file
> set. On Windows, I don't get an error from pswrite ("psgray" not
> included), but no output is produced; *nix version could have a
> different behaviour.
>

Genius!!

You are both right!!
Dan was right, but had a typo, which I was too dumb too spot.
Using Dan's information (output name before input name) and fixing
the typo gives me success. I can proceed! Life is good.

Thanks to all.

BugBear

Sponsored Links