Re^4: [OT] Code that writes code that writes code: Perl to Lisp to Postscript

in reply to Re^3: [OT] Code that writes code that writes code: Perl to Lisp to Postscript
in thread Code that writes code that writes code: Perl to Lisp to Postscript

I bow to the excellence of you code!! Well I would if my back didn't hurt. This is such an advance over my effort that I will with your permission and with suitable credit steal this code for my Lisp package. Theft is the highest praise for someone else's work ;) This comes at a particularly opportune time— I've decided to forgo the use of the figurine fonts in favor of the ordinary fonts; i.e. LinaresFigurine ⇒ Linares. I'm doing this because this lets me mix normal text and figurine in one font. Your block_justify is just the thing to fold into the mix with this change. I'll update this node with the new result.

Liking Postscript as you do, have you ever tried Forth? My only complaint about Postscript is that Warnock should have copied all of the Forth vocabulary not just some. Cool thing is that, that is easily fixable using the language itself

--hsm

"Never try to teach a pig to sing...it wastes your time and it annoys the pig."

Comment on Re^4: [OT] Code that writes code that writes code: Perl to Lisp to Postscript Download Code

Replies are listed 'Best First'.
Re^5: [OT] Code that writes code that writes code: Perl to Lisp to Postscript by almut (Canon) on Apr 29, 2008 at 17:56 UTC
Theft is the highest praise for someone else's work ;) True words :) Thanks! — feel free to use it in whatever way you like. BTW, under these new circumstances I should mention there is a little peculiarity. That is, you need a trailing space at the end of the text (noticed the space in `"laborum. ) def"`? - that's there on purpose). The space itself will not be visible, but without it, the last line might not wrap properly in some cases. (I've always wanted to fix this bug, but then again, making sure there is that space has always been easier... ;) As to Forth, yes I've tried it and generally liked it. Though, due to largely missing library functionality in the environment I used at the time, it has always been somewhat tedious to get any real world problem solved with it... That definitely is a plus of PS, its powerful builtin typesetting and graphics facilities.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: [OT] Code that writes code that writes code: Perl to Lisp to Postscript
by almut (Canon) on Apr 29, 2008 at 17:56 UTC

Theft is the highest praise for someone else's work ;)

True words :) Thanks! — feel free to use it in whatever way you like.

BTW, under these new circumstances I should mention there is a little peculiarity. That is, you need a trailing space at the end of the text (noticed the space in "laborum. ) def"? - that's there on purpose). The space itself will not be visible, but without it, the last line might not wrap properly in some cases. (I've always wanted to fix this bug, but then again, making sure there is that space has always been easier... ;)

As to Forth, yes I've tried it and generally liked it. Though, due to largely missing library functionality in the environment I used at the time, it has always been somewhat tedious to get any real world problem solved with it... That definitely is a plus of PS, its powerful builtin typesetting and graphics facilities.

[reply]
[d/l]

In Section Cool Uses for Perl