comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » idl / psutils
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
idl / psutils [message #27978] Thu, 15 November 2001 00:35 Go to next message
R.Bauer is currently offline  R.Bauer
Messages: 1424
Registered: November 1998
Senior Member
Hi,


please can someone else do a small test to convert
an idl ps file with ps2epsi into an eps which was created by IDL5.5.

(psutils 1.7)

> ps2epsi idl.ps idl.eps


If I do so I got an error which I don't understand.

sed: -e expression #2, char 15: Extra characters after command


If I do the same with IDL5.4.1 I have no problems.


I don't know which is wrong and what to do. A bug in idl Postscript
a feature or something else might be possible.


Any ideas,

regards

Reimar


--
Reimar Bauer

Institut fuer Stratosphaerische Chemie (ICG-1)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
http://www.fz-juelich.de/icg/icg1/
============================================================ ======
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml

http://www.fz-juelich.de/zb/text/publikation/juel3786.html
============================================================ ======

read something about linux / windows
http://www.suse.de/de/news/hotnews/MS.html
Re: idl / psutils [message #28057 is a reply to message #27978] Thu, 15 November 2001 12:36 Go to previous message
nobody@nowhere.com (S is currently offline  nobody@nowhere.com (S
Messages: 55
Registered: July 2001
Member
On Thu, 15 Nov 2001 19:15:36 +0100, Reimar Bauer <r.bauer@fz-juelich.de> wrote:
> "Steve Smith" wrote:
>>
>> on our GIF license before upgrading to IDL 5.5 :^) ! But, ps2epsi is just a
>> script which calls ghostscript, there is only one line in it that uses sed:
>>
>> sed -e '/^%%BeginPreview:/,/%%EndPreview$/d' -e '/^%!PS-Adobe/d'\
>> -e '/^%%[A-Za-z][A-Za-z]*$/d' -e '/^%%[A-Za-z][A-Za-z]*: /d'
>>
>> It sounds like expression #2 is after the second -e, and maybe your sed
>> doesn't like the newline ( the \ ), so you could try to put all the
>> commands in the ps2epsi script on one line?
>
> Dear Steve,
>
> exactly this was the solution. But on both machines is the same sed.
> The difference is in the ghostscript. So I have not tried this before.
>
> Thanks
>
> Reimar
>
>

it's nice to fix something, even if you don't know how it works ... it does
keep one awake at night, however!

--
Steve S.

steve@NOSPAMmailaps.org
remove NOSPAM before replying
Re: idl / psutils [message #28058 is a reply to message #27978] Thu, 15 November 2001 10:15 Go to previous message
R.Bauer is currently offline  R.Bauer
Messages: 1424
Registered: November 1998
Senior Member
"Steve Smith" wrote:
>
> On Thu, 15 Nov 2001 09:35:59 +0100, Reimar Bauer <r.bauer@fz-juelich.de> wrote:
>> Hi,
>>
>>
>> please can someone else do a small test to convert
>> an idl ps file with ps2epsi into an eps which was created by IDL5.5.
>>
>> (psutils 1.7)
>>
>>> ps2epsi idl.ps idl.eps
>>
>>
>> If I do so I got an error which I don't understand.
>>
>> sed: -e expression #2, char 15: Extra characters after command
>>
>
> Sorry, I can't try it, I'm still waiting for our legal department to comment
> on our GIF license before upgrading to IDL 5.5 :^) ! But, ps2epsi is just a
> script which calls ghostscript, there is only one line in it that uses sed:
>
> sed -e '/^%%BeginPreview:/,/%%EndPreview$/d' -e '/^%!PS-Adobe/d'\
> -e '/^%%[A-Za-z][A-Za-z]*$/d' -e '/^%%[A-Za-z][A-Za-z]*: /d'
>
> It sounds like expression #2 is after the second -e, and maybe your sed
> doesn't like the newline ( the \ ), so you could try to put all the
> commands in the ps2epsi script on one line?

Dear Steve,

exactly this was the solution. But on both machines is the same sed.
The difference is in the ghostscript. So I have not tried this before.

Thanks

Reimar


>
> sed is a stream editing tool, you can see that it's just looking at the
> postscript prolouge (think that's what it's called). Unfortunately, sed
> commands look so much like postscript commands, I can't guess off hand
> what it's actually doing here, so I can't tell you what's happening. Logan
> may laud me for tinkering till I figured it out, but it's a small consolation
> for enduring disciplinary action for spending too much time on it! Hopefully
> there's something here you didn't know already :^), I would just open the
> ps file and see what it looks like, and compare with your old ps output
> (from prior version of IDL). You could also check the faq at the sed web
> site mentioned in the sed man pages.
>
> --
> Steve S.
>
> steve@NOSPAMmailaps.org
> remove NOSPAM before replying

--
Reimar Bauer

Institut fuer Stratosphaerische Chemie (ICG-1)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
http://www.fz-juelich.de/icg/icg1/
============================================================ ======
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml

http://www.fz-juelich.de/zb/text/publikation/juel3786.html
============================================================ ======

read something about linux / windows
http://www.suse.de/de/news/hotnews/MS.html
Re: idl / psutils [message #28062 is a reply to message #27978] Thu, 15 November 2001 08:48 Go to previous message
nobody@nowhere.com (S is currently offline  nobody@nowhere.com (S
Messages: 55
Registered: July 2001
Member
On Thu, 15 Nov 2001 09:35:59 +0100, Reimar Bauer <r.bauer@fz-juelich.de> wrote:
> Hi,
>
>
> please can someone else do a small test to convert
> an idl ps file with ps2epsi into an eps which was created by IDL5.5.
>
> (psutils 1.7)
>
>> ps2epsi idl.ps idl.eps
>
>
> If I do so I got an error which I don't understand.
>
> sed: -e expression #2, char 15: Extra characters after command
>

Sorry, I can't try it, I'm still waiting for our legal department to comment
on our GIF license before upgrading to IDL 5.5 :^) ! But, ps2epsi is just a
script which calls ghostscript, there is only one line in it that uses sed:

sed -e '/^%%BeginPreview:/,/%%EndPreview$/d' -e '/^%!PS-Adobe/d'\
-e '/^%%[A-Za-z][A-Za-z]*$/d' -e '/^%%[A-Za-z][A-Za-z]*: /d'

It sounds like expression #2 is after the second -e, and maybe your sed
doesn't like the newline ( the \ ), so you could try to put all the
commands in the ps2epsi script on one line?

sed is a stream editing tool, you can see that it's just looking at the
postscript prolouge (think that's what it's called). Unfortunately, sed
commands look so much like postscript commands, I can't guess off hand
what it's actually doing here, so I can't tell you what's happening. Logan
may laud me for tinkering till I figured it out, but it's a small consolation
for enduring disciplinary action for spending too much time on it! Hopefully
there's something here you didn't know already :^), I would just open the
ps file and see what it looks like, and compare with your old ps output
(from prior version of IDL). You could also check the faq at the sed web
site mentioned in the sed man pages.

--
Steve S.

steve@NOSPAMmailaps.org
remove NOSPAM before replying
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: IDL Runtime
Next Topic: HASP/ flexLM licensing conflict

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:01:57 PDT 2025

Total time taken to generate the page: 0.00645 seconds