From cph at chi-square-works.com  Wed Aug 18 19:04:25 2004
From: cph at chi-square-works.com (Chisheng Huang)
Date: Wed, 18 Aug 2004 19:04:25 +0000 (GMT)
Subject: [cl-pdf-devel] cl-pdf examples not working in cmucl 19a
Message-ID: <E1BxVjz-0000b2-00@common-lisp.net>

Hi,

I downloaded cl-pdf-current.tgz yesterday and managed to get
it compiled and loaded on a Red Hat 7.3 box with
  1. CMUCL 19a (x86 Linux) plus contrib/zlib-cmucl.lisp
  2. LispWorks personal edition 4.3.6. plus contrib/zlib-lw.lisp

All examples in examples/examples.lisp work in Lispworks but none
of them work in CMUCL.  The backtrace of running EXAMPLE1 is attached 
at the end of this email.  I'll be grateful if someone can show me how
to get around this problem.

I'm sorry if this is not the right place to ask this type of questions.

Best wishes,

-cph

-------------------- backtrace --------------------

#<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}> cannot be printed readably.
   [Condition of type PRINT-NOT-READABLE]

Restarts:
  0: [ABORT] Abort handling SLIME request.
  1:         Return to Top-Level.

Debug  (type H for help)

(LISP::%PRINT-UNREADABLE-OBJECT #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}> #<String-Output Stream> NIL T ...)
Source: 
; File: target:code/print.lisp
(ERROR (QUOTE PRINT-NOT-READABLE) :OBJECT OBJECT)
0] back

0: (LISP::%PRINT-UNREADABLE-OBJECT #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}> #<String-Output Stream> NIL T ...)
1: (LISP::OUTPUT-LIST (SETF (PCL::STD-INSTANCE-WRAPPER PCL::.INSTANCE.) #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}>) #<String-Output Stream>)
2: (LISP::OUTPUT-LIST (LET (# #) (SETF # #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}>) (SETF # PCL::.SLOTS.) (LET NIL #) ...) #<String-Output Stream>)
3: (LISP::OUTPUT-LIST (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)) #<String-Output Stream>)
4: (PRIN1 (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)) #<String-Output Stream>)
5: (FORMAT::S-FORMAT-DIRECTIVE-INTERPRETER #<String-Output Stream> #<~S> (#<~^> " ") #<unused-arg> ...)
6: (FORMAT::INTERPRET-DIRECTIVE-LIST #<String-Output Stream> (#<~S> #<~^> " ") (FUNCTION (KERNEL:INSTANCE-LAMBDA # #)) ((KERNEL:INSTANCE-LAMBDA # #)))
7: ((LABELS FORMAT::DO-LOOP FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER) (FUNCTION (KERNEL:INSTANCE-LAMBDA # #)) ((KERNEL:INSTANCE-LAMBDA # #)))
8: (FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER #<String-Output Stream> #<~{> (#<~S> #<~^> " " #<~}> #<~^> ...) ((FUNCTION #)) ...)
9: (FORMAT::INTERPRET-DIRECTIVE-LIST #<String-Output Stream> (#<~{> #<~S> #<~^> " " #<~}> ...) ((FUNCTION #)) ((FUNCTION #)))
10: ((LABELS FORMAT::DO-LOOP FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER) ((FUNCTION #)) ((FUNCTION #)))
11: (FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER #<String-Output Stream> #<~{> (#<~{> #<~S> #<~^> " " #<~}> ...) ((#)) ...)
12: (FORMAT::INTERPRET-DIRECTIVE-LIST #<String-Output Stream> (#<~{> #<~{> #<~S> #<~^> " " ...) ((#)) ((#)))
13: (FORMAT::%FORMAT #<String-Output Stream> "~{~{~S~^ ~}~^ => ~}" ((#)) ((#)))
14: (FORMAT NIL "~{~{~S~^ ~}~^ => ~}" ((FUNCTION #)))
15: (C::FIND-COMPONENT-NAME #<C:COMPONENT 58F62F5D  NAME= "<unknown>">)
16: (C::FIND-TOP-LEVEL-COMPONENTS (#<C:COMPONENT 58F62F5D  NAME= "<unknown>"> #<C:COMPONENT 58F6353D  NAME= "<unknown>">))
17: ((FLET #:G0 COMPILE))
18: (COMPILE (MAKE-INSTANCE PDF::NAMED-REFERENCE :NAME PCL::|.P0.|) (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)))
19: (COMPILE 2 (MAKE-INSTANCE PDF::NAMED-REFERENCE :NAME PCL::|.P0.|) (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)))[:EXTERNAL]
20: (PCL::COMPILE-LAMBDA (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)) :NAME (MAKE-INSTANCE PDF::NAMED-REFERENCE :NAME PCL::|.P0.|) :INLINE ...)
21: ((LABELS PCL::INSTALL PCL::INSTALL-OPTIMIZED-CONSTRUCTOR) T)
22: ("DEFUN INSTALL-INITIAL-CONSTRUCTOR" "R101")
23: (PDF:GET-NAMED-REFERENCE "R101")
24: (PDF::REGISTER-NAMED-REFERENCE #(#<PDF::PAGE {58E9C755}> "/Fit") "R101")
25: (PDF:REGISTER-PAGE-REFERENCE "R101")
26: ("DEFUN EXAMPLE1")
27: (LISP::%WITH-STANDARD-IO-SYNTAX #<Function "DEFUN EXAMPLE1" {58B290B1}>)
28: (EXAMPLE1 #p"/tmp/ex1.pdf")




From marc.battyani at fractalconcept.com  Wed Aug 18 19:35:24 2004
From: marc.battyani at fractalconcept.com (Marc Battyani)
Date: Wed, 18 Aug 2004 21:35:24 +0200
Subject: [cl-pdf-devel] cl-pdf examples not working in cmucl 19a
References: <E1BxVjz-0000b2-00@common-lisp.net>
Message-ID: <05b501c4855a$83632440$0a02a8c0@marcxp>

Chisheng Huang wrote:
>
> I downloaded cl-pdf-current.tgz yesterday and managed to get
> it compiled and loaded on a Red Hat 7.3 box with
>   1. CMUCL 19a (x86 Linux) plus contrib/zlib-cmucl.lisp
>   2. LispWorks personal edition 4.3.6. plus contrib/zlib-lw.lisp
>
> All examples in examples/examples.lisp work in Lispworks but none
> of them work in CMUCL.  The backtrace of running EXAMPLE1 is attached
> at the end of this email.  I'll be grateful if someone can show me how
> to get around this problem.
>
> I'm sorry if this is not the right place to ask this type of questions.

This is the right place to ask this kind of questions.
Unfortunately, I'm not a CMUCL user so I can't help you on this.
(cl-pdf and cl-typesetting used to work on the previous versions of CMUCL
though)

All the Best,

Marc




From david.cooper at genworks.com  Wed Aug 18 20:19:59 2004
From: david.cooper at genworks.com (David J Cooper Jr)
Date: Wed, 18 Aug 2004 16:19:59 -0400
Subject: [cl-pdf-devel] cl-pdf examples not working in cmucl 19a
In-Reply-To: <E1BxVjz-0000b2-00@common-lisp.net>
References: <E1BxVjz-0000b2-00@common-lisp.net>
Message-ID: <16675.47599.746206.964215@mccarthy.genworks.com>



Hello cl-pdfers,

I have seen the kind of error Chisheng refers to below in Allegro as
well, and I believe it is due to the

   with-standard-io-syntax 

in pdf.lisp which binds *print-readably* to T. 

I have added a

 ....
  (let (*print-readably*)
  ....

within the with-standard-io-syntax in order to suppress the
*print-readably* being T, and I question whether we really need
*print-readably* set to T by default throughout cl-pdf and
cl-typesetting (it was added in release 2.1 of cl-pdf with
explanation:

    Added a few with-standard-io-syntax so that the pdf are generated
    correctly when people change the printer settings.

I'm not sure what this means with respect to *print-readably* being T
or NIL however. With *print-readably* T it makes, for example,
printing debug output difficult since object instances generally
cannot be printed without doing something extra (a print-object
method?)

Thanks,

 -dave



Chisheng Huang writes:
 > Hi,
 > 
 > I downloaded cl-pdf-current.tgz yesterday and managed to get
 > it compiled and loaded on a Red Hat 7.3 box with
 >   1. CMUCL 19a (x86 Linux) plus contrib/zlib-cmucl.lisp
 >   2. LispWorks personal edition 4.3.6. plus contrib/zlib-lw.lisp
 > 
 > All examples in examples/examples.lisp work in Lispworks but none
 > of them work in CMUCL.  The backtrace of running EXAMPLE1 is attached 
 > at the end of this email.  I'll be grateful if someone can show me how
 > to get around this problem.
 > 
 > I'm sorry if this is not the right place to ask this type of questions.
 > 
 > Best wishes,
 > 
 > -cph
 > 
 > -------------------- backtrace --------------------
 > 
 > #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}> cannot be printed readably.
 >    [Condition of type PRINT-NOT-READABLE]
 > 
 > Restarts:
 >   0: [ABORT] Abort handling SLIME request.
 >   1:         Return to Top-Level.
 > 
 > Debug  (type H for help)
 > 
 > (LISP::%PRINT-UNREADABLE-OBJECT #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}> #<String-Output Stream> NIL T ...)
 > Source: 
 > ; File: target:code/print.lisp
 > (ERROR (QUOTE PRINT-NOT-READABLE) :OBJECT OBJECT)
 > 0] back
 > 
 > 0: (LISP::%PRINT-UNREADABLE-OBJECT #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}> #<String-Output Stream> NIL T ...)
 > 1: (LISP::OUTPUT-LIST (SETF (PCL::STD-INSTANCE-WRAPPER PCL::.INSTANCE.) #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}>) #<String-Output Stream>)
 > 2: (LISP::OUTPUT-LIST (LET (# #) (SETF # #<Wrapper #<STANDARD-CLASS PDF::NAMED-REFERENCE {580778ED}> {5806B115}>) (SETF # PCL::.SLOTS.) (LET NIL #) ...) #<String-Output Stream>)
 > 3: (LISP::OUTPUT-LIST (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)) #<String-Output Stream>)
 > 4: (PRIN1 (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)) #<String-Output Stream>)
 > 5: (FORMAT::S-FORMAT-DIRECTIVE-INTERPRETER #<String-Output Stream> #<~S> (#<~^> " ") #<unused-arg> ...)
 > 6: (FORMAT::INTERPRET-DIRECTIVE-LIST #<String-Output Stream> (#<~S> #<~^> " ") (FUNCTION (KERNEL:INSTANCE-LAMBDA # #)) ((KERNEL:INSTANCE-LAMBDA # #)))
 > 7: ((LABELS FORMAT::DO-LOOP FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER) (FUNCTION (KERNEL:INSTANCE-LAMBDA # #)) ((KERNEL:INSTANCE-LAMBDA # #)))
 > 8: (FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER #<String-Output Stream> #<~{> (#<~S> #<~^> " " #<~}> #<~^> ...) ((FUNCTION #)) ...)
 > 9: (FORMAT::INTERPRET-DIRECTIVE-LIST #<String-Output Stream> (#<~{> #<~S> #<~^> " " #<~}> ...) ((FUNCTION #)) ((FUNCTION #)))
 > 10: ((LABELS FORMAT::DO-LOOP FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER) ((FUNCTION #)) ((FUNCTION #)))
 > 11: (FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER #<String-Output Stream> #<~{> (#<~{> #<~S> #<~^> " " #<~}> ...) ((#)) ...)
 > 12: (FORMAT::INTERPRET-DIRECTIVE-LIST #<String-Output Stream> (#<~{> #<~{> #<~S> #<~^> " " ...) ((#)) ((#)))
 > 13: (FORMAT::%FORMAT #<String-Output Stream> "~{~{~S~^ ~}~^ => ~}" ((#)) ((#)))
 > 14: (FORMAT NIL "~{~{~S~^ ~}~^ => ~}" ((FUNCTION #)))
 > 15: (C::FIND-COMPONENT-NAME #<C:COMPONENT 58F62F5D  NAME= "<unknown>">)
 > 16: (C::FIND-TOP-LEVEL-COMPONENTS (#<C:COMPONENT 58F62F5D  NAME= "<unknown>"> #<C:COMPONENT 58F6353D  NAME= "<unknown>">))
 > 17: ((FLET #:G0 COMPILE))
 > 18: (COMPILE (MAKE-INSTANCE PDF::NAMED-REFERENCE :NAME PCL::|.P0.|) (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)))
 > 19: (COMPILE 2 (MAKE-INSTANCE PDF::NAMED-REFERENCE :NAME PCL::|.P0.|) (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)))[:EXTERNAL]
 > 20: (PCL::COMPILE-LAMBDA (KERNEL:INSTANCE-LAMBDA (PCL::|.P0.|) (LET # # # # ...)) :NAME (MAKE-INSTANCE PDF::NAMED-REFERENCE :NAME PCL::|.P0.|) :INLINE ...)
 > 21: ((LABELS PCL::INSTALL PCL::INSTALL-OPTIMIZED-CONSTRUCTOR) T)
 > 22: ("DEFUN INSTALL-INITIAL-CONSTRUCTOR" "R101")
 > 23: (PDF:GET-NAMED-REFERENCE "R101")
 > 24: (PDF::REGISTER-NAMED-REFERENCE #(#<PDF::PAGE {58E9C755}> "/Fit") "R101")
 > 25: (PDF:REGISTER-PAGE-REFERENCE "R101")
 > 26: ("DEFUN EXAMPLE1")
 > 27: (LISP::%WITH-STANDARD-IO-SYNTAX #<Function "DEFUN EXAMPLE1" {58B290B1}>)
 > 28: (EXAMPLE1 #p"/tmp/ex1.pdf")
 > 
 > 
 > _______________________________________________
 > cl-pdf-devel site list
 > cl-pdf-devel at common-lisp.net
 > http://common-lisp.net/mailman/listinfo/cl-pdf-devel
 > 
 > 




From marc.battyani at fractalconcept.com  Wed Aug 18 20:47:34 2004
From: marc.battyani at fractalconcept.com (Marc Battyani)
Date: Wed, 18 Aug 2004 22:47:34 +0200
Subject: [cl-pdf-devel] cl-pdf examples not working in cmucl 19a
References: <E1BxVjz-0000b2-00@common-lisp.net>
	<16675.47599.746206.964215@mccarthy.genworks.com>
Message-ID: <008801c48564$98842f40$0a04a8c0@marcxp>

David J Cooper Jr wrote:

> I have seen the kind of error Chisheng refers to below in Allegro as
> well, and I believe it is due to the
>
>    with-standard-io-syntax
>
> in pdf.lisp which binds *print-readably* to T.
>
> I have added a
>
>  ....
>   (let (*print-readably*)
>   ....
>
> within the with-standard-io-syntax in order to suppress the
> *print-readably* being T, and I question whether we really need
> *print-readably* set to T by default throughout cl-pdf and
> cl-typesetting (it was added in release 2.1 of cl-pdf with
> explanation:
>
>     Added a few with-standard-io-syntax so that the pdf are generated
>     correctly when people change the printer settings.
>
> I'm not sure what this means with respect to *print-readably* being T
> or NIL however. With *print-readably* T it makes, for example,
> printing debug output difficult since object instances generally
> cannot be printed without doing something extra (a print-object
> method?)

At least one cl-pdf user uses radix 16 by default. So the pdf files were not
very readable by acrobat ;-)
But you are right, *print-readably* should be nil. Anyway, maybe there is
some bug hiding here, especially if you get a similar error with ACL.

Marc




From peter at javamonkey.com  Wed Aug 18 20:57:35 2004
From: peter at javamonkey.com (Peter Seibel)
Date: Wed, 18 Aug 2004 13:57:35 -0700
Subject: [cl-pdf-devel] cl-pdf examples not working in cmucl 19a
In-Reply-To: <008801c48564$98842f40$0a04a8c0@marcxp> (Marc Battyani's
	message of "Wed, 18 Aug 2004 22:47:34 +0200")
References: <E1BxVjz-0000b2-00@common-lisp.net>
	<16675.47599.746206.964215@mccarthy.genworks.com>
	<008801c48564$98842f40$0a04a8c0@marcxp>
Message-ID: <m38yccw4e8.fsf@javamonkey.com>

"Marc Battyani" <marc.battyani at fractalconcept.com> writes:

> At least one cl-pdf user uses radix 16 by default. So the pdf files
> were not very readable by acrobat ;-) But you are right,
> *print-readably* should be nil.

Seems like The Right Thing would be to define something like this
macro:

  (defmaco with-pdf-io-syntax (&body body)
    `(with-standard-io-syntax
       (let ((*print-readably* nil))
         , at body)))

and then use it where appropriate. Then if it turns out that we also
want to bind some other printer control variable differently than
standard-io-syntax we just change the definition of this macro and
we're done.

-Peter

-- 
Peter Seibel                                      peter at javamonkey.com

         Lisp is the red pill. -- John Fraser, comp.lang.lisp



From brian.sorg at liberatinginsight.com  Sun Aug 22 00:08:49 2004
From: brian.sorg at liberatinginsight.com (Brian Sorg)
Date: Sat, 21 Aug 2004 19:08:49 -0500
Subject: [cl-pdf-devel] Cl-pdf & cl-typesetting usage documentation expanded
Message-ID: <4127E411.9040208@liberatinginsight.com>

Hello everyone,

I just wanted to let you know that I have released a major upgrade to 
the usage documentation for cl-pdf and cl-typesetting. It is based on 
version 2.1 and documents most of features that one would use to create 
a pdf document.  It can be found at 
www.liberatinginsight.com/open-projects.html.  There you can view the 
documentation online or download a zip file.  The documentation is html 
formatted.

If anyone finds mistakes or has information to add please let me know.

The next steps I plan to take are to:

1. Create a few short tutorials by solving typical problems, ie business 
letters, avery label creation, etc
2. Update the documentation to match the current release
3. Document the remaining features
4. Generate the documentation using cl-typesetting

 

Brian Sorg
Director: Liberating Insight LLC
Office: 260-745-2211
Mobile: 260-602-1086
Fax: 614-839-9208
www.LiberatingInsight.com





From marc.battyani at fractalconcept.com  Mon Aug 30 22:05:55 2004
From: marc.battyani at fractalconcept.com (Marc Battyani)
Date: Tue, 31 Aug 2004 00:05:55 +0200
Subject: [cl-pdf-devel] Re: [cl-typesetting-devel] Cl-pdf & cl-typesetting
	usage documentation expanded
References: <4127E411.9040208@liberatinginsight.com>
Message-ID: <0fbf01c48edd$87ae7310$0a02a8c0@marcxp>

"Brian Sorg" <brian.sorg at liberatinginsight.com> wrote:

#|
Sorry for the reply delay but your ISP refuses my emails to you and the
mailing lists were down :(
|#

> I just wanted to let you know that I have released a major upgrade to
> the usage documentation for cl-pdf and cl-typesetting. It is based on
> version 2.1 and documents most of features that one would use to create
> a pdf document.  It can be found at
> www.liberatinginsight.com/open-projects.html.  There you can view the
> documentation online or download a zip file.  The documentation is html
> formatted.

Cool!

> If anyone finds mistakes or has information to add please let me know.
>
> The next steps I plan to take are to:
>
> 1. Create a few short tutorials by solving typical problems, ie business
> letters, avery label creation, etc

Good, this is really missing for now.

> 2. Update the documentation to match the current release

It's still a moving target...

> 3. Document the remaining features

Good.

> 4. Generate the documentation using cl-typesetting

Yes, this one is a must ;-)

Have you got some feedback on this ?
(Well, probably not. I have lots of downloads for my open-source projects
but
almost never any feedback :()

Automatic documentation generation is a topic I will probably add to
cl-typesetting. I've already added graph generation/typesetting and tomorrow
I will release a cl-typesetting pretty printer for lisp files. This could be
combined with some XRef utilities in the CMU Lisp repository or with
something like Albert for some cute documentation generation.

Any volunteers to help ?

Marc