Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #719
| From | Helge Blischke <h.blischke@acm.org> |
|---|---|
| Newsgroups | comp.lang.postscript |
| Subject | Re: Why do I not see the characters |
| Followup-To | comp.lang.postscript |
| Date | 2012-06-09 22:24 +0200 |
| Message-ID | <a3hpn5ForiU1@mid.individual.net> (permalink) |
| References | <87r4to6ddr.fsf@Compaq.site> <878vfw66a3.fsf@Compaq.site> <2012060907184822140-john@acumentrainingcom> <87fwa4s7cf.fsf@Compaq.site> |
Followups directed to: comp.lang.postscript
Cecil Westerhof wrote: > 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.) > Well, epstopdf calls Ghostscript with the option "-dSAFER" which denies most file access, especially write acdcess. Helge
Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Why do I not see the characters Cecil Westerhof <Cecil@decebal.nl> - 2012-06-09 11:30 +0200
Re: Why do I not see the characters Cecil Westerhof <Cecil@decebal.nl> - 2012-06-09 14:04 +0200
Re: Why do I not see the characters John Deubert <john@acumentraining.com> - 2012-06-09 07:18 -0700
Re: Why do I not see the characters Cecil Westerhof <Cecil@decebal.nl> - 2012-06-09 19:50 +0200
Re: Why do I not see the characters Helge Blischke <h.blischke@acm.org> - 2012-06-09 22:24 +0200
Re: Why do I not see the characters luser- -droog <mijoryx@yahoo.com> - 2012-06-09 10:14 -0700
Re: Why do I not see the characters Cecil Westerhof <Cecil@decebal.nl> - 2012-06-09 22:16 +0200
Re: Why do I not see the characters luser- -droog <mijoryx@yahoo.com> - 2012-06-09 14:16 -0700
Re: Why do I not see the characters Cecil Westerhof <Cecil@decebal.nl> - 2012-06-10 00:15 +0200
Re: Why do I not see the characters luser- -droog <mijoryx@yahoo.com> - 2012-06-09 15:51 -0700
Re: Why do I not see the characters luser- -droog <mijoryx@yahoo.com> - 2012-06-09 10:24 -0700
csiph-web