Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail
From: Cecil Westerhof <Cecil@decebal.nl>
Newsgroups: comp.lang.postscript
Subject: Re: Why do I not see the characters
Date: Sat, 09 Jun 2012 19:50:08 +0200
Organization: Decebal Computing
Lines: 50
Message-ID: <87fwa4s7cf.fsf@Compaq.site>
References: <87r4to6ddr.fsf@Compaq.site> <878vfw66a3.fsf@Compaq.site> <2012060907184822140-john@acumentrainingcom>
NNTP-Posting-Host: lYLrXPFpjyZ8237ODaoN+w.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
X-Notice: Filtered by postfilter v. 0.8.2
Cancel-Lock: sha1:I6JAjfATRYgoBx8gD/jtuGvzwEE=
X-Homepage: http://www.decebal.nl/
Xref: csiph.com comp.lang.postscript:716

Op zaterdag 9 jun 2012 16:18 CEST schreef John Deubert:

> By "library" do you mean PS code stored on your hard disk?

Yes, exactly. I do not want to copy that code every time. The program
looks less and when I make a change …


> If so, you can store the code in a .ps file and execute it from within
> another PS program with the "run" operator:
>
> 	(myLibraryCode.ps) run
>
> As you can see, "run" is the PS equivalent of "#include."
>
> The only tricky bit is figuring out what directory on your disk epstopdf
> considers to be its "home" directory, that is, where it will look for
> the myLibraryCode.ps file. It may be the directory in which the epstopdf
> executable resides; that's common, but by no means the only possibility.
> One way to ferret this out is to make a file from within a PS program
> and see where the file shows up on your disk. Try this:
>
> % ====Cut here======
> (TestFile.txt)(w) file
> dup (This is a test.) writestring
> closefile
> % ====Cut here======
>
> Run this program and see where the TestFile.txt file shows up; that's
> the home directory.

That gives:
    Error: /invalidfileaccess in --file--
    Operand stack:
       (TestFile.txt)   (w)

Exactly what I got before. As I understand it epstopdf does not allow
file access for security reasons.


> There's a detailed article on this in the January 2002 issue of the
> Acumen Journal (free for the downloading here:
> www.acumentraining.com/acumenjournal.html)

I will look at it. (And the other stuff.)

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof