World: r3wp

How to generate portable Postscript

Do not explicitly specify paper format. 
 Unfortunately, many programs 
force you to select a paper size. Often, it can be edited out of 
the Postscript file. Instead, let the printer decide whether it can 
print a document with specific dimensions.

It's an old document, from 2000, though...

I'm just wondering what the default page size is, when it's not specified.

pagesize: 595x842  ; Default A4 page size
img: help.gif
offset: 0x0

write/binary %test-image.ps postscript compose/deep [DeviceRGB [translate 
(as-pair offset/x pagesize/y - offset/y - img/size/y) scale 36x36 
image img]]

kghostview test-image.ps  shows the help.gif image just down a little 
bit from the top-left of the page. I suppose it's a margin of some 
sort.

Hmm.. if I have
	offset: pagesize - img/size

then it shows the image just a little left of bottom-right corner 
of page.
Another margin ?

Anyway... just a little dabble in the postscript world..

the only problem with switchy is that everything is upside down, 
inclusing text.

Geomol, I've added direct support for image! in the postscript dialect. 
It seemed appropriate to do.

Henrik, I can see, there's a bit difference in our versions. Maybe 
we should merge at some point? Image is in both our versions though.

I was editing 0.4.3 from February 2008. Is yours newer?

No, same version:
http://home.tiscali.dk/john.niclasen/postscript/postscript.r

I mean, I haven't done anything else with it since.

I remember images working fine this spring, but it does not work 
now. I'm wondering what's wrong.

Ok, what do you wanna do? Anton did a little test, that worked ok. 
I can run the test here too.

I want to do the equivalent of what anton did above, just with to-postscript.

then we can compare

http://rebol.hmkdesign.dk/files/test.ps

That one fails here.

to-postscript layout/tight [text "Page 1" image help.gif]

That's the code for it

Geomol, the code for image that is in your version is:

image: [err:
	'image set name [file! | url! | word!] (

  img: either word! = type? name [get name] [load-image/update name]
		x: img/size/x
		y: img/size/y

I've changed that to:

image: [err:

 'image [set img [file! | url!] (img: load-image/update img) | set 
 img word! (img: get img) | set img image!] (
		x: img/size/x
		y: img/size/y

When I run your test with my version of postscript.r, I get a page 
with a gray box in upper left and the text "Page 1". It's an ok PS 
file here.

Should I see the help.gif image too?

yes, it should be there.

Ghostscript will not run that file here.

ah wait... let me check if your version of to-postscript properly 
supports images

it was wrong. please try again.

Doesn't work with my version of postscript. Why is the image change 
needed?

because otherwise I can't put images directly into the dialect and 
I will have to store them in a tempory place first and reference 
them with a word => much more code.

the changes I listed above adds image! support directly..

Ah, got it. *thinking*

With the change, I can produce a PS file, but I still can't see the 
image. Will try some stuff...

There should not be any change in my version of the image decoder.

Does this work for you?


write %imagetest.ps postscript [DeviceRGB [translate 100x600 scale 
100x100 image help.gif]]

Yes, I had to add DeviceRGB to see the image.

yes, it works

DeviceRGB is already added here. Is scale necessary?

Think so. :)

Yes, so your image is there, it's just tiny.

well, it still won't run the PS file.

Use scale 72x72 for 72 dpi.

back in 30 mins.

Henrik, I think, you need another factor. The one you have now, is 
set to 1. It's ok for your text. You have to put scale 72x72 (or 
something) when showing images.

I tried setting your factor to 72, then I can see the image, but 
the text is HUGE! :-)

BTW, if you don't mind: I've added a probe on the dialect code output 
in to-postscript.r. Then you can see if I'm writing something incorrect 
out.

interesting that you can run the file. I can't.

and I've already added scaling

I had a problem some time ago showing PS files, I produced. I think, 
it was some cache.

The dialect code, you produce, looks ok. I'm really not a shark with 
PS, so it doesn't mean, it's 100%, even if it looks ok to me. :)

Best way is to test, test, test, I'm afraid.