World: r3wp

But I think we should strive to remove all brackets [ .. ] from the 
dialect.

Maybe we can take a look at some examples of real PS output from 
different apps?

Do we need to do that?

As long as we can satisfy out aims of text on paper, and some graphics 
...

The idea with the brackets come from the term "path" in PS. I had 
the feeling, that paths could hold lots of content. Maybe looking 
at other PS output can tell us something about that?

Ahh..

If we end up with lots of paths in our PS files, other might say, 
we produce bloath PS.

my output file is a little shorter than yours, but only because I 
didn't bother creating the prolog / epilog

I think to create those should be a refinement.

because you might only want to create a short postscript fragment 
rather than a script.

yes

We need information about, what can be inside one path, and how they 
are used in other PS files.

In my lates PS output, there is also a problem, where the box and 
the filled box is made. The box ends with a closepath and a stroke, 
but there is no newpath to start the next. I think, that's not 100% 
correct, but it seems to work.

I didn't even use 'newpath !  :(

Ok, definitely need to find out when a newpath command is needed.

presumably, stroke, fill, and show close the existing path.

I read somewhere, that some PS operators force newpath, but it's 
bad practice to leave them out.

maybe just make 'newpath a part of the dialect as well.

That is a problem, because we then leave it up to the user to make 
sure, the rules of PS holds. That's the same as writing PS directly, 
so not much is won.

A good dialect is one with some simple rules, and where it's difficult 
to produce something wrong.

We just need to know a little more, then we can make it almost perfect.

:)

I'm too tired now and am going to bed. Good night!

night

but it makes it easier to program :)

is it me or does translate not work?

I never got as far as implementing translate.  But John's has it.

it's john's version I'm trying it in

mine works .. I'll upload it.

test3: form ps/header [
	gsave
	translate 72x72
	at 0x0 box 72x72 stroke
	grestore
	showpage
]

draws a box at 72x72 where origin is translated to 72x72

test3: form ps/header [
	gsave
	translate 72x72
	newpath
	at 0x0 box 72x72 stroke
	grestore
	showpage
]

{%!
%%Creator: ps.r ver 0.0.4
gsave
72 72 translate
newpath
0 0 moveto 72 0 rlineto 0 72 rlineto -72 0 rlineto closepath
stroke
grestore
showpage

%%EOF

ah, the good old copy trap. for the zillionth time I fell in.

wait for R3 then!

this has to be working by april 22nd. so that's no go.

watcha doing?

that barcode thing.

ahh...

just numbers?

or full alphabet?

yes

no

you can't use a postscript barcode font?

no, the barcode is already working fine. it's the position of the 
image on the paper and general arrangement of the code that needs 
to be worked out

oh well, good luck.

thanks

oh, how are you doing the image in postscript ?

just drawing lots of parallel lines

ok, there's a hex format for images as well as using eps, but I don't 
know how that works.