World: r3wp

what I do to cause the error is make a ps file with postscript.r 
and then feed it directly to the printer. In windows I print directly 
to LPT1: to produce it. Under Linux I print it via LPR.

I've seen the bug in two separate HP laser printers

no, sorry, under Linux I also print to the device directly. LPR was 
when I used PDF for printing rather than PS.

a simple check: does a PS example from the internet end the same 
way as a postscript.r generated file?

Output from TextEdit printed to a PS file has this in the end:

%%Trailer
%%Pages: 1
%%EOF
^D


The last char (ctrl-D) is hex 04. I think, the comment lines are 
according to "PostScript Language Document Structuring Conventions 
Specification". You can find this document on the net at Adobe. So 
there is a difference in how %%Pages comments are handled. And postscript.r 
doesn't put hex 04 in the end. You could try some of these changes, 
when you have the problem.

I'll give it a shot when I get access to the testing equipment.

Updated the documentation:
http://home.tiscali.dk/john.niclasen/postscript/postscript.html
Added describtion of comment.

Has anyone tried the transformations? There might be an unwanted 
restriction in the implementation. I can't get transformations to 
work for a whole page, only for one path at a time.

I've only tried transformations for single paths, sorry.

Do you use right-aligned text?

it has worked fine in the past, I believe

Yes, but it only worked with integer! text-size. I've added decimal! 
option, and this seems to work too. (sub-unit precision)
I have a new version ready soon.

cool :-)

I needed the decimal! for text size in alignment, because postscript 
work with 72 dot pr. inch by default. Putting text on the page often 
need the text to be with sub-unit precision. It was possible to put 
the text with sub-unit before, but now also alignment can be with 
sub-unit precision.

anyone been working on a postscript table generator for the dialet?

dialect

Geomol. have you been looking at vertically centered text? It could 
be added as a y parameter to 'text, where we already use an x parameter 
for the string box size.

No, I don't think, I've looked at that yet. I might tomorrow.

That is the big problem, basically, that as in going across pages 
(or being wide).

I think I have a crude way to do it for one line.

need it for table cells

I'm working on displaying Qwikis (Wikis) on Cell phones.


It is a connected problem, viewing something intended for one medium 
on another.  

My basic plan is:


- Images - make a thumbnail, then let them click on it to see a larger 
or a list of sizes of their choice


- Tables - Show the name of the table, and then a bias, column or 
row, and offer a search.  Then drill down.


When printing big tables to paper you have to decide what to do if 
the table is simply too big for a single piece of paper.

Put the table at the end on multiple pages?

Put a small version of the table (perhaps unreadable), and say "See 
table on Exhibit X"?
Put the table on multiple pages inline?

Convert the table to something else, for example more like a query 
result, where each row is a chunk of data in a new format?

looks like getting something so simple as the font height is rather 
difficult in postscript

huh?

Geomol, I have the structure change needed for text to support the 
font height, so the vertical centering can be made, but I just can't 
find the postscript commands necessary to obtain the font height.

you define the font height when you set the font.

and there are postscript commands for getting the size of the text

the width of the text yes, not the height. and I may not know the 
font at rendering time as that may be set in a completely different 
part of the program.

not sure about that .. but you can set a postscript variable to hold 
the latest fontsize and reference that

/fontsize (size) def

I seem to remember justification routines get the word size, drop 
the height value and just work on the width

stringwidth returns the width and some form of Y value that is not 
the height, but something else.

it's the offset from the baseline

The ``charpath'' operator extracts the graphic shapes of its string 
operand and appends them to the current path in the graphic state. 
These shapes can then be processed by other PostScript operators. 
To get the actual size of the area touched by a character a simple 
approach is

	gsave
	newpath
	0 0 moveto
	(X) false charpath flattenpath pathbbox
	grestore


This code places four numbers on the stack, representing the coordinates 
of the lower left and upper right corners of the bounding box enclosing 
the character ``X'' rendered with the current point at (0,0). Leaving 
the flattenpath out will cause it to be less accurate, but it will 
take up less memory and be faster.

how do I call it again, with /fontsize or fontsize?

tried that one, couldn't get it to work.

though not in that form

faq: http://www.postscript.org/FAQs/language/node67.html

nope, that doesn't work either

what do you mean it doesn't work?

I get a postscript error.

Got the font size to work, but it doesn't take the baseline into 
account.

time for bed... Geomol can take over in the morning. :-)

aren't you both in the same timezone?

yes

yes! got grahams method working now. thanks.

it also helps better top alignment

Geomol, you may find my changes here:

http://hmkdesign.dk/rebol/postscript.r

The changes are:


- Stores the font size inside PS every time a new font is selected. 
This is not used however, but perhaps is useful in the future.

- Added bottom, middle and top alignment for TEXT. Similarly to how 
you specify a size for LEFT, CENTER and RIGHT, you can enter a size 
for TOP, MIDDLE and BOTTOM:

Some text
 center 400 middle 200

Both sets are optional. The default alignment is LEFT and BOTTOM.

My changes are marked HMK in the source. I hope it is of use.

now it would be nice with some form of margin management