From attila.lendvai at gmail.com Fri Dec 1 17:58:34 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Fri, 1 Dec 2006 18:58:34 +0100 Subject: [cl-pdf-devel] two small patches In-Reply-To: References: Message-ID: hi! please find two patches attached for cl-pdf and cl-typesetting. they are mostly small cleanups, getting rid of warnings. and one of them was even a bug: a possible rename left-over of trimmable-white-space-p. there are two TODO comments in the patches, where i was not sure how to fix the code. Marc, please take a look at them. and a suggestion: i think it's not a good idea to include salza and iterate in the repo. salza is asdf-installable now, and iterate even has a public darcs repo. hth, -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) -------------- next part -------------- A non-text attachment was scrubbed... Name: cl-pdf.diff Type: text/x-patch Size: 21530 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cl-typesetting.diff Type: text/x-patch Size: 13646 bytes Desc: not available URL: From marc.battyani at fractalconcept.com Fri Dec 1 22:29:19 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Fri, 1 Dec 2006 23:29:19 +0100 Subject: [cl-pdf-devel] two small patches References: Message-ID: <04ca01c71598$27772340$1402a8c0@marcx2> "Attila Lendvai" > please find two patches attached for cl-pdf and cl-typesetting. they > are mostly small cleanups, getting rid of warnings. and one of them > was even a bug: a possible rename left-over of trimmable-white-space-p. Thanks, I've accumulated several patches so far and I do feel the growing need to find some time to apply and test them. > there are two TODO comments in the patches, where i was not sure how > to fix the code. Marc, please take a look at them. OK. > and a suggestion: i think it's not a good idea to include salza and > iterate in the repo. salza is asdf-installable now, and iterate even > has a public darcs repo. Well I've been burnt by independent libraries changing and breaking code. This is why I've added Iterate and Salza in cl-pdf. Maybe I could move it to the same level as cl-pdf so that people can have access to a working configuration but use another one if they want. Marc From attila.lendvai at gmail.com Sat Dec 2 21:24:26 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Sat, 2 Dec 2006 22:24:26 +0100 Subject: [cl-pdf-devel] two small patches In-Reply-To: <04ca01c71598$27772340$1402a8c0@marcx2> References: <04ca01c71598$27772340$1402a8c0@marcx2> Message-ID: > Well I've been burnt by independent libraries changing and breaking code. > This is why I've added Iterate and Salza in cl-pdf. Maybe I could move it to > the same level as cl-pdf so that people can have access to a working > configuration but use another one if they want. a possible solution for this and also to the lack of your time sorting out patches would be to give write access to some old-time contributors. if i were you i would just ask for a project from Erik at common-lisp.net and move the pdf/typesetting repos there. then have the oldtimers be added to the unix group and expect things to happen without my own work... :) in my experience it also speeds up the development of the libs by lowering the cost of sending patches and the delay they get applied. only some of my 0.02 that i always share, even when i wasn't asked... :) -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From marc.battyani at fractalconcept.com Sat Dec 2 22:17:20 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sat, 2 Dec 2006 23:17:20 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2> Message-ID: <078c01c7165f$a2528650$1402a8c0@marcx2> Attila Lendvai wrote: >> Well I've been burnt by independent libraries changing and breaking code. >> This is why I've added Iterate and Salza in cl-pdf. Maybe I could move it >> to >> the same level as cl-pdf so that people can have access to a working >> configuration but use another one if they want. > > a possible solution for this and also to the lack of your time sorting > out patches would be to give write access to some old-time > contributors. if i were you i would just ask for a project from Erik > at common-lisp.net and move the pdf/typesetting repos there. then have > the oldtimers be added to the unix group and expect things to happen > without my own work... :) > > in my experience it also speeds up the development of the libs by > lowering the cost of sending patches and the delay they get applied. Well why not? So who wants an SVN account with modification rights on cl-pdf, cl-typesetting and mod_lisp ;-) Attila? Dmitryi? Marc From attila.lendvai at gmail.com Sat Dec 2 22:56:31 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Sat, 2 Dec 2006 23:56:31 +0100 Subject: [cl-pdf-devel] two small patches In-Reply-To: <078c01c7165f$a2528650$1402a8c0@marcx2> References: <04ca01c71598$27772340$1402a8c0@marcx2> <078c01c7165f$a2528650$1402a8c0@marcx2> Message-ID: > Well why not? > > So who wants an SVN account with modification rights on cl-pdf, > cl-typesetting and mod_lisp ;-) > > Attila? Dmitryi? well, i can certainly offer a hand or two! especially that we've just started to use these libs more extensively and i have write access to one of the dependencies, iterate, too... :) if you are thinking in cl.net, my account is alendvai there. normally i'm way too liberal in refactoring for most people's taste. usually i'm not restraining from breaking backward compatibility, if that makes the code cleaner. but for obvious reasons that's not always desirable. but i guess it will work out, i'll keep my hands off at the beginning and ask here on the list for opinions and/or send offensive changes first for review. but please do warn me if you ever find that i'm shaping things too liberally! so i can hold back my horses.... darcs would be a big help in that with it's patchset based internal logic, but i was bugging so many projects with moving to darcs lately that i hardly dare to bring it up anymore. i can offer a repo conversion to darcs, but i promise you'll hear no more words from me regarding this... :) -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From peter at gigamonkeys.com Sat Dec 2 23:57:42 2006 From: peter at gigamonkeys.com (Peter Seibel) Date: Sat, 2 Dec 2006 15:57:42 -0800 Subject: [cl-pdf-devel] two small patches In-Reply-To: <078c01c7165f$a2528650$1402a8c0@marcx2> References: <04ca01c71598$27772340$1402a8c0@marcx2> <078c01c7165f$a2528650$1402a8c0@marcx2> Message-ID: <174C0035-7499-49D0-9B08-423E94AE749E@gigamonkeys.com> On Dec 2, 2006, at 2:17 PM, Marc Battyani wrote: > Attila Lendvai wrote: > > >>> Well I've been burnt by independent libraries changing and >>> breaking code. >>> This is why I've added Iterate and Salza in cl-pdf. Maybe I could >>> move it to >>> the same level as cl-pdf so that people can have access to a working >>> configuration but use another one if they want. >> >> a possible solution for this and also to the lack of your time >> sorting >> out patches would be to give write access to some old-time >> contributors. if i were you i would just ask for a project from Erik >> at common-lisp.net and move the pdf/typesetting repos there. then >> have >> the oldtimers be added to the unix group and expect things to happen >> without my own work... :) >> >> in my experience it also speeds up the development of the libs by >> lowering the cost of sending patches and the delay they get applied. > > Well why not? > > So who wants an SVN account with modification rights on cl-pdf, cl- > typesetting and mod_lisp ;-) > > Attila? Dmitryi? I might have a patch to contribute from time to time, if it was easy. -Peter From gwking at metabang.com Sun Dec 3 03:27:55 2006 From: gwking at metabang.com (Gary King) Date: Sat, 2 Dec 2006 22:27:55 -0500 Subject: [cl-pdf-devel] two small patches In-Reply-To: References: <04ca01c71598$27772340$1402a8c0@marcx2> <078c01c7165f$a2528650$1402a8c0@marcx2> Message-ID: <6F2F5994-1C26-4199-8A69-8160086468EA@metabang.com> Hi Marc, I've been hoping/meaning/wishing to add PDF support to CL-Markdown for a while now and CL-PDF / CL-Typesetting is definitely how I'm going to do that. I'm quite swamped at the moment but I'd be interested in having rights (and with rights come responsibilities! ). FWIW, I use darcs for all my projects and am quite happy with it. On Dec 2, 2006, at 5:56 PM, Attila Lendvai wrote: >> Well why not? >> >> So who wants an SVN account with modification rights on cl-pdf, >> cl-typesetting and mod_lisp ;-) >> >> Attila? Dmitryi? > > well, i can certainly offer a hand or two! especially that we've just > started to use these libs more extensively and i have write access to > one of the dependencies, iterate, too... :) if you are thinking in > cl.net, my account is alendvai there. > > normally i'm way too liberal in refactoring for most people's taste. > usually i'm not restraining from breaking backward compatibility, if > that makes the code cleaner. but for obvious reasons that's not always > desirable. but i guess it will work out, i'll keep my hands off at the > beginning and ask here on the list for opinions and/or send offensive > changes first for review. but please do warn me if you ever find that > i'm shaping things too liberally! so i can hold back my horses.... > > darcs would be a big help in that with it's patchset based internal > logic, but i was bugging so many projects with moving to darcs lately > that i hardly dare to bring it up anymore. i can offer a repo > conversion to darcs, but i promise you'll hear no more words from me > regarding this... :) > > -- > - attila > > "- The truth is that I've been too considerate, and so became > unintentionally cruel... > - I understand. > - No, you don't understand! We don't speak the same language!" > (Ingmar Bergman - Smultronst?llet) > _______________________________________________ > cl-pdf-devel site list > cl-pdf-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/cl-pdf-devel -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM From marc.battyani at fractalconcept.com Sun Dec 3 10:16:08 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 3 Dec 2006 11:16:08 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2> <078c01c7165f$a2528650$1402a8c0@marcx2> Message-ID: <08a201c716c4$0cbc0c00$1402a8c0@marcx2> Attila Lendvai wrote: > normally i'm way too liberal in refactoring for most people's taste. > usually i'm not restraining from breaking backward compatibility, if > that makes the code cleaner. but for obvious reasons that's not always > desirable. but i guess it will work out, i'll keep my hands off at the > beginning and ask here on the list for opinions and/or send offensive > changes first for review. but please do warn me if you ever find that > i'm shaping things too liberally! so i can hold back my horses.... Well, I have cl-pdf/cl-typesetting in my production code repository so I'm not too much scared. But try to not break the code anyway. ;-) I will send you a login/password on my svn repository. > darcs would be a big help in that with it's patchset based internal > logic, but i was bugging so many projects with moving to darcs lately > that i hardly dare to bring it up anymore. i can offer a repo > conversion to darcs, but i promise you'll hear no more words from me > regarding this... :) Well it's svn it's already better than cvs anyway. I will not use darcs before it is usable as well on linux than on windows and is as cool as tortoisesvn on win platforms. ;-) Marc From marc.battyani at fractalconcept.com Sun Dec 3 10:36:06 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 3 Dec 2006 11:36:06 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2><078c01c7165f$a2528650$1402a8c0@marcx2> <6F2F5994-1C26-4199-8A69-8160086468EA@metabang.com> Message-ID: <08f601c716c6$d6b94430$1402a8c0@marcx2> Gary King wrote: >I've been hoping/meaning/wishing to add PDF support to CL-Markdown >for a while now and CL-PDF / CL-Typesetting is definitely how I'm >going to do that. I'm quite swamped at the moment but I'd be >interested in having rights (and with rights come responsibilities! >). Great. I've send you a passwd. :) >FWIW, I use darcs for all my projects and am quite happy with it. I just replied to Attila on that subject. Marc From marc.battyani at fractalconcept.com Sun Dec 3 10:41:00 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 3 Dec 2006 11:41:00 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2> <078c01c7165f$a2528650$1402a8c0@marcx2> <001601c716b0$e12d5c50$8100a8c0@digo> Message-ID: <090101c716c7$86367f90$1402a8c0@marcx2> Dmitriy Ivanov wrote: > |> in my experience it also speeds up the development of the libs by > |> lowering the cost of sending patches and the delay they get applied. > | > | Well why not? > | > | So who wants an SVN account with modification rights on cl-pdf, > | cl-typesetting and mod_lisp ;-) > | > | Attila? Dmitryi? > > OT1H, I prefer the situation where one person is responsible for a > library. > Otherwise, project code is becoming more and more like spaghetti. IMHO, > this > has happened to many large open source projects. I prefer this way too but I have to admit that I don't have the time to do it well enough. :-( > OTOH, I have been actually maintaining versions of CL-PDF and > CL-TYPESETTING > of my own for more than one year :-(. So getting feedback on my code from > other people would not that bad. OK, I sent you a password. Marc From marc.battyani at fractalconcept.com Sun Dec 3 11:03:15 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 3 Dec 2006 12:03:15 +0100 Subject: [cl-pdf-devel] cl-pdf/cl-typesetting/mod_lisp repository guidelines. References: <04ca01c71598$27772340$1402a8c0@marcx2><078c01c7165f$a2528650$1402a8c0@marcx2><6F2F5994-1C26-4199-8A69-8160086468EA@metabang.com> <08f601c716c6$d6b94430$1402a8c0@marcx2> Message-ID: <091e01c716ca$a169d160$1402a8c0@marcx2> Hello to the new committers, Now that you have commit rights on the cl-pdf/cl-typesetting/mod_lisp repository let's define a few guidelines to avoid a complete mess ;-) I just propose 2 guidelines: 1 - As Gary wrote don't forget that with rights come responsibilities! So test your code before you commit it... ;-) 2 - If you make a major change, like converting cl-pdf to full binary format for instance, please make a new branch so that people can test and eventually fix it before it is merged back to the official branch. Also, though it's not a rule, you should probably inform this list of what you are working on to avoid duplicate work and/or incompatible modifications. Have fun! :) Marc From marc.battyani at fractalconcept.com Sun Dec 3 11:23:45 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 3 Dec 2006 12:23:45 +0100 Subject: [cl-pdf-devel] cl-pdf/cl-typesetting/mod_lisp repository guidelines. References: <04ca01c71598$27772340$1402a8c0@marcx2><078c01c7165f$a2528650$1402a8c0@marcx2><6F2F5994-1C26-4199-8A69-8160086468EA@metabang.com><08f601c716c6$d6b94430$1402a8c0@marcx2> <091e01c716ca$a169d160$1402a8c0@marcx2> Message-ID: <094701c716cd$7eec4a70$1402a8c0@marcx2> I wrote: > Hello to the new committers, > > Now that you have commit rights on the cl-pdf/cl-typesetting/mod_lisp > repository let's define a few guidelines to avoid a complete mess ;-) > > I just propose 2 guidelines: > > 1 - As Gary wrote don't forget that with rights come responsibilities! So > test your code before you commit it... ;-) > > 2 - If you make a major change, like converting cl-pdf to full binary > format for instance, please make a new branch so that people can test and > eventually fix it before it is merged back to the official branch. > > Also, though it's not a rule, you should probably inform this list of what > you are working on to avoid duplicate work and/or incompatible > modifications. > > Have fun! :) Let's add this one too: When you commit something please start the commit message wtih the module name (i.e. cl-pdf: ... cl-typesetting:...) so that it's easier to search for a change in the logs. Marc From divanov at aha.ru Mon Dec 4 07:56:14 2006 From: divanov at aha.ru (Dmitriy Ivanov) Date: Mon, 4 Dec 2006 10:56:14 +0300 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2> <078c01c7165f$a2528650$1402a8c0@marcx2> Message-ID: <000101c71779$b3bf7860$8100a8c0@digo> Hello Marc, |> in my experience it also speeds up the development of the libs by |> lowering the cost of sending patches and the delay they get applied. | | Well why not? | | So who wants an SVN account with modification rights on cl-pdf, | cl-typesetting and mod_lisp ;-) | | Attila? Dmitryi? OT1H, I prefer the situation where one person is responsible for a library. Otherwise, project code is becoming more and more like spaghetti. IMHO, this has happened to many large open source projects. OTOH, I have been actually maintaining versions of CL-PDF and CL-TYPESETTING of my own for more than one year :-(. So getting feedback on my code from other people would not that bad. -- Sincerely, Dmitriy Ivanov lisp.ystok.ru From jcm at FreeBSD-uk.eu.org Sat Dec 9 16:01:32 2006 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Sat, 9 Dec 2006 16:01:32 +0000 Subject: [cl-pdf-devel] two small patches In-Reply-To: <04ca01c71598$27772340$1402a8c0@marcx2> References: <04ca01c71598$27772340$1402a8c0@marcx2> Message-ID: <20061209160132.GB77846@dogma.freebsd-uk.eu.org> Are you planning on regularly syncing the 'official' release tarball with the development version? I don't feel like running subversion on all my boxes. ;-P Jonathon McKitrick -- My other computer is your Windows box. From marc.battyani at fractalconcept.com Sat Dec 9 16:07:30 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sat, 9 Dec 2006 17:07:30 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2> <20061209160132.GB77846@dogma.freebsd-uk.eu.org> Message-ID: <040c01c71bac$24091b90$1402a8c0@marcx2> "Jonathon McKitrick" wrote: > > Are you planning on regularly syncing the 'official' release tarball with > the > development version? I don't feel like running subversion on all my > boxes. > ;-P Yes, it's already the case. But so far nobody has commited anything yet... Marc From attila.lendvai at gmail.com Sat Dec 9 16:21:43 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Sat, 9 Dec 2006 17:21:43 +0100 Subject: [cl-pdf-devel] two small patches In-Reply-To: <040c01c71bac$24091b90$1402a8c0@marcx2> References: <04ca01c71598$27772340$1402a8c0@marcx2> <20061209160132.GB77846@dogma.freebsd-uk.eu.org> <040c01c71bac$24091b90$1402a8c0@marcx2> Message-ID: > Yes, it's already the case. But so far nobody has commited anything yet... sorry for being this slow, but could you please help me in how to use my password? i assume it's an ssh login and i must use something along the line: svn checkout svn+ssh://www.fractalconcept.com/public/open-source/cl-typesetting/ but i couldn't figure it out... :| -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From dave at genworks.com Sat Dec 9 21:16:18 2006 From: dave at genworks.com (Dave Cooper) Date: Sat, 9 Dec 2006 16:16:18 -0500 Subject: [cl-pdf-devel] two small patches In-Reply-To: References: <04ca01c71598$27772340$1402a8c0@marcx2> <20061209160132.GB77846@dogma.freebsd-uk.eu.org> <040c01c71bac$24091b90$1402a8c0@marcx2> Message-ID: <30eff3110612091316o52936c02u61a4f4047153be8f@mail.gmail.com> > > sorry for being this slow, but could you please help me in how to use > my password? > You use the --username argument to svn, then it will prompt you for your password if you are doing anything which modifies the repository. You only have to give the username and password once per client machine per repository, then they get stored for future uses. For example, I just checked out cl-pdf, make a slight modification to the to-do.txt, then commited rev. 121, as follows: svn co http://www.fractalconcept.com:8000/public/open-source/cl-pdf cl-pdf --username dave.cooper # [This did not prompt me for password, but it did store my name dave.cooper for future operations on my local cl-pdf working directory] cd cl-pdf # [then I edited to-do.txt] svn commit -m"added one item to the to-do.txt" # [Now it prompted me for my password] So now when I do subsequent "svn update" and "svn commit" from my local cl-pdf directory, it shouldn't prompt me for anything. Other useful commands with svn are: svn status svnversion These two commands do not require a connection to the repository. -dave -- Dave Cooper dave at genworks.com 248-932-2166(o), 248-330-2979(c), 1-800-731-9220(toll-free in North America) From marc.battyani at fractalconcept.com Sun Dec 10 09:52:36 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 10 Dec 2006 10:52:36 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2><20061209160132.GB77846@dogma.freebsd-uk.eu.org><040c01c71bac$24091b90$1402a8c0@marcx2> <30eff3110612091316o52936c02u61a4f4047153be8f@mail.gmail.com> Message-ID: <053401c71c40$ef4e28b0$1402a8c0@marcx2> "Dave Cooper" wrote: >> sorry for being this slow, but could you please help me in how to use >> my password? >> > > You use the --username argument to svn, then it will prompt you for > your password if you are doing anything which modifies the repository. > > You only have to give the username and password once per client > machine per repository, then they get stored for future uses. > > For example, I just checked out cl-pdf, make a slight modification to > the to-do.txt, then commited rev. 121, as follows: > > > svn co http://www.fractalconcept.com:8000/public/open-source/cl-pdf > cl-pdf --username dave.cooper It's better to get the whole repository so that cl-pdf and cl-typesetting stay in sync on the local side: i.e. use /public/open-source/ rather than /public/open-source/cl-pdf To avoid sending the password in clear, I've setup an HTTPS connection on: https://www.fractalconcept.com:8001/public/open-source/ The Marc From attila.lendvai at gmail.com Sun Dec 10 22:44:35 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Sun, 10 Dec 2006 23:44:35 +0100 Subject: [cl-pdf-devel] two small patches In-Reply-To: <053401c71c40$ef4e28b0$1402a8c0@marcx2> References: <04ca01c71598$27772340$1402a8c0@marcx2> <20061209160132.GB77846@dogma.freebsd-uk.eu.org> <040c01c71bac$24091b90$1402a8c0@marcx2> <30eff3110612091316o52936c02u61a4f4047153be8f@mail.gmail.com> <053401c71c40$ef4e28b0$1402a8c0@marcx2> Message-ID: > It's better to get the whole repository so that cl-pdf and cl-typesetting > stay in sync on the local side: > i.e. use /public/open-source/ rather than /public/open-source/cl-pdf > > To avoid sending the password in clear, I've setup an HTTPS connection on: > https://www.fractalconcept.com:8001/public/open-source/ thanks a lot for both of you for the svn help! i've committed my small cleanups that should not affect neither lib, mostly just get rid of warnings, keep global variables unbound for early failing when rebinding is forgotten, and small stuff like that. i've added two TODO annotations, where i couldn't decide for myself whether the warning is inappropriate or there's a bug. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From attila.lendvai at gmail.com Sun Dec 10 22:48:32 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Sun, 10 Dec 2006 23:48:32 +0100 Subject: [cl-pdf-devel] file encoding in the repo Message-ID: emacs is crying that it can't decode the project files in utf-8. if there's no objection for long enough then i'll eventually convert the files that contain non-ascii chard in the repo to utf-8. if the conversion is not desirable, alternatively we could annotate the encoding in a comment that emacs can pick up. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From attila.lendvai at gmail.com Sun Dec 10 22:52:04 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Sun, 10 Dec 2006 23:52:04 +0100 Subject: [cl-pdf-devel] iterate and salza dependency Message-ID: i'm planning to drop iterate and salza from the repository. if noone vetos it for long enough i'll get to it eventually. i always needed to modify my local copy not to load the iterate.asd because it caused various headaches. please speak up if you have any objections! -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From marc.battyani at fractalconcept.com Sun Dec 10 22:58:43 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 10 Dec 2006 23:58:43 +0100 Subject: [cl-pdf-devel] two small patches References: <04ca01c71598$27772340$1402a8c0@marcx2><20061209160132.GB77846@dogma.freebsd-uk.eu.org><040c01c71bac$24091b90$1402a8c0@marcx2><30eff3110612091316o52936c02u61a4f4047153be8f@mail.gmail.com><053401c71c40$ef4e28b0$1402a8c0@marcx2> Message-ID: <098901c71cae$c0f90160$1402a8c0@marcx2> "Attila Lendvai" wrote: >> It's better to get the whole repository so that cl-pdf and cl-typesetting >> stay in sync on the local side: >> i.e. use /public/open-source/ rather than /public/open-source/cl-pdf >> >> To avoid sending the password in clear, I've setup an HTTPS connection >> on: >> https://www.fractalconcept.com:8001/public/open-source/ > > thanks a lot for both of you for the svn help! > > i've committed my small cleanups that should not affect neither lib, > mostly just get rid of warnings, keep global variables unbound for > early failing when rebinding is forgotten, and small stuff like that. Great! Thanks for all those small fixes. I've a quick glance at them and it seems OK for me. > i've added two TODO annotations, where i couldn't decide for myself > whether the warning is inappropriate or there's a bug. Where? (The logs are unusable as you modified all the files... ;-) Marc From marc.battyani at fractalconcept.com Sun Dec 10 23:00:17 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Mon, 11 Dec 2006 00:00:17 +0100 Subject: [cl-pdf-devel] file encoding in the repo References: Message-ID: <09ba01c71cae$f888f180$1402a8c0@marcx2> "Attila Lendvai" wrote: > emacs is crying that it can't decode the project files in utf-8. > > if there's no objection for long enough then i'll eventually convert > the files that contain non-ascii chard in the repo to utf-8. > > if the conversion is not desirable, alternatively we could annotate > the encoding in a comment that emacs can pick up. I don't see what you mean. I use emacs and have no problems so far. Marc From marc.battyani at fractalconcept.com Sun Dec 10 23:02:26 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Mon, 11 Dec 2006 00:02:26 +0100 Subject: [cl-pdf-devel] iterate and salza dependency References: Message-ID: <09c401c71caf$458e32b0$1402a8c0@marcx2> "Attila Lendvai" wrote: > i'm planning to drop iterate and salza from the repository. if noone > vetos it for long enough i'll get to it eventually. i always needed to > modify my local copy not to load the iterate.asd because it caused > various headaches. > > please speak up if you have any objections! No problem for Iterate but IIRC Salza have been very much optimized so it's not the same as Zach one. Marc From attila.lendvai at gmail.com Sun Dec 10 23:15:21 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Mon, 11 Dec 2006 00:15:21 +0100 Subject: [cl-pdf-devel] iterate and salza dependency In-Reply-To: <09c401c71caf$458e32b0$1402a8c0@marcx2> References: <09c401c71caf$458e32b0$1402a8c0@marcx2> Message-ID: > No problem for Iterate but IIRC Salza have been very much optimized so it's > not the same as Zach one. oh, i didn't know that. then first i'll look into sending a patch in your name for Zach. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From peter at gigamonkeys.com Wed Dec 13 00:16:42 2006 From: peter at gigamonkeys.com (Peter Seibel) Date: Tue, 12 Dec 2006 16:16:42 -0800 Subject: [cl-pdf-devel] pdf:draw-text question Message-ID: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> Is it by design that pdf:draw-text doesn't take care of escaping dangerous characters (such as #\( and #\))? It's easy enough to deal from outside, now that I know what the problem is, but I was surprised to discover garbage in my PDF output when I tried to (pdf:draw-text "(something"). -Peter From divanov at aha.ru Wed Dec 13 07:35:14 2006 From: divanov at aha.ru (Dmitriy Ivanov) Date: Wed, 13 Dec 2006 10:35:14 +0300 Subject: [cl-pdf-devel] pdf:draw-text question References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> Message-ID: <000001c71e8a$7633e0e0$8100a8c0@digo> Hello Peter, | Is it by design that pdf:draw-text doesn't take care of escaping | dangerous characters (such as #\( and #\))? It's easy enough to deal | from outside, now that I know what the problem is, but I was | surprised to discover garbage in my PDF output when I tried to | (pdf:draw-text "(something"). Yes. In the version of CL-PDF of my own, draw-text does escape but show-text and other functions in the show-... family do not. If that would publicly accepted, I would speed up committing my new contribution code. -- Sincerely, Dmitriy Ivanov lisp.ystok.ru From marc.battyani at fractalconcept.com Wed Dec 13 10:38:52 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Wed, 13 Dec 2006 11:38:52 +0100 Subject: [cl-pdf-devel] pdf:draw-text question References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> Message-ID: <00b201c71ea2$e20a4e90$1402a8c0@marcx2> Dmitriy Ivanov wrote: > Hello Peter, > > | Is it by design that pdf:draw-text doesn't take care of escaping > | dangerous characters (such as #\( and #\))? It's easy enough to deal > | from outside, now that I know what the problem is, but I was > | surprised to discover garbage in my PDF output when I tried to > | (pdf:draw-text "(something"). At the beginning draw-text and such functions were supposed to be just a temporary hack before switching to some cl-typesetting based functions. But it looks like that finally they are here to stay. > Yes. In the version of CL-PDF of my own, draw-text does escape but > show-text > and other functions in the show-... family do not. If that would publicly > accepted, I would speed up committing my new contribution code. OK for me. Marc From divanov at aha.ru Wed Dec 13 18:01:33 2006 From: divanov at aha.ru (Dmitriy Ivanov) Date: Wed, 13 Dec 2006 21:01:33 +0300 Subject: [cl-pdf-devel] Big contibution committed References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> <00b201c71ea2$e20a4e90$1402a8c0@marcx2> Message-ID: <000701c71ee0$bdff9620$8100a8c0@digo> Hello folks, I have just committed a good deal of code. The main change is a new encoding scheme. The functions write-cid-string and write-cid-char are not actually used any longer. They were replaced by the corresponding methods on write-to-page, an new generic function. For implementations other than LispWorks, these methods must be augmented appropriately. I have rewritten the file encodings.lisp completely. Rather than erase old definitions in other files, I retained them but marked by #+old-pdf-encoding. Small patches, e.g. pdf:draw-text, are also included. The code was tested on LWW 4.4.6. I have successfully run examples 1 through 7. Example8 contains latin-1 characters which is converted to Unicode due to my locale. Please try yourselves. I have not tested Unicode fonts myself. Update carefully :-) -- Sincerely, Dmitriy Ivanov lisp.ystok.ru From attila.lendvai at gmail.com Wed Dec 13 19:11:43 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Wed, 13 Dec 2006 20:11:43 +0100 Subject: [cl-pdf-devel] Big contibution committed In-Reply-To: <000701c71ee0$bdff9620$8100a8c0@digo> References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> <00b201c71ea2$e20a4e90$1402a8c0@marcx2> <000701c71ee0$bdff9620$8100a8c0@digo> Message-ID: > I have successfully run examples 1 through 7. Example8 contains latin-1 > characters which is converted to Unicode due to my locale. Please try > yourselves. great! i've not noticed any regression on sbcl, but i still can't write unicode into pdf with typesetting. i get the utf-8 double chars, even though i belive i've opened a bivalent stream with iso-8859-2 encoding (on sbcl). i'll further investigate this, but if somone has a working unicode example it would be cool if it was committed into the repo. and i also suggest to decide on an "official" lisp file encoding for the repo to avoid problems like you have with example8 (those chars decode to some chinese unicode chars when decoded in utf-8). i suggest utf-8 for this, because that is the default at most places. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From marc.battyani at fractalconcept.com Wed Dec 13 21:21:29 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Wed, 13 Dec 2006 22:21:29 +0100 Subject: [cl-pdf-devel] Big contibution committed References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com><000001c71e8a$7633e0e0$8100a8c0@digo><00b201c71ea2$e20a4e90$1402a8c0@marcx2> <000701c71ee0$bdff9620$8100a8c0@digo> Message-ID: <01a601c71efc$ab128ce0$1402a8c0@marcx2> Dmitriy Ivanov wrote: > Hello folks, > > I have just committed a good deal of code. The main change is a new > encoding > scheme. > > The functions write-cid-string and write-cid-char are not actually used > any > longer. They were replaced by the corresponding methods on write-to-page, > an > new generic function. For implementations other than LispWorks, these > methods must be augmented appropriately. > > I have rewritten the file encodings.lisp completely. Rather than erase old > definitions in other files, I retained them but marked by > #+old-pdf-encoding. > > Small patches, e.g. pdf:draw-text, are also included. > > The code was tested on LWW 4.4.6. > > I have successfully run examples 1 through 7. Example8 contains latin-1 > characters which is converted to Unicode due to my locale. Please try > yourselves. > > I have not tested Unicode fonts myself. > > Update carefully :-) Cool! Big commit for sure. ;-) I've look at it but not tested it yet. Marc From marc.battyani at fractalconcept.com Wed Dec 13 21:41:30 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Wed, 13 Dec 2006 22:41:30 +0100 Subject: [cl-pdf-devel] Big contibution committed References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com><000001c71e8a$7633e0e0$8100a8c0@digo><00b201c71ea2$e20a4e90$1402a8c0@marcx2><000701c71ee0$bdff9620$8100a8c0@digo> Message-ID: <01d901c71eff$766961a0$1402a8c0@marcx2> Attila Lendvai wrote: >> I have successfully run examples 1 through 7. Example8 contains latin-1 >> characters which is converted to Unicode due to my locale. Please try >> yourselves. > > great! i've not noticed any regression on sbcl, but i still can't > write unicode into pdf with typesetting. i get the utf-8 double chars, > even though i belive i've opened a bivalent stream with iso-8859-2 > encoding (on sbcl). i'll further investigate this, but if somone has a > working unicode example it would be cool if it was committed into the > repo. > > and i also suggest to decide on an "official" lisp file encoding for > the repo to avoid problems like you have with example8 (those chars > decode to some chinese unicode chars when decoded in utf-8). i suggest > utf-8 for this, because that is the default at most places. Well maybe this can cause problems with non unicode. I just removed the French text in example8 so it's simpler that way. Marc From divanov at aha.ru Thu Dec 14 09:13:23 2006 From: divanov at aha.ru (Dmitriy Ivanov) Date: Thu, 14 Dec 2006 12:13:23 +0300 Subject: [cl-pdf-devel] Big contibution committed References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> <00b201c71ea2$e20a4e90$1402a8c0@marcx2> <000701c71ee0$bdff9620$8100a8c0@digo> Message-ID: <000001c71f70$d80edf40$8100a8c0@digo> "Attila Lendvai" wrote: | great! i've not noticed any regression on sbcl, but i still can't | write unicode into pdf with typesetting. i get the utf-8 double chars, | even though i belive i've opened a bivalent stream with iso-8859-2 | encoding (on sbcl). i'll further investigate this, but if somone has a | working unicode example it would be cool if it was committed into the | repo. | | and i also suggest to decide on an "official" lisp file encoding for | the repo to avoid problems like you have with example8 (those chars | decode to some chinese unicode chars when decoded in utf-8). i suggest | utf-8 for this, because that is the default at most places. utf-8 is hardly supported in PDF. I would suggest switching to UCS-2 instead. -- Sincerely, Dmitriy Ivanov lisp.ystok.ru From peter at gigamonkeys.com Thu Dec 14 16:56:17 2006 From: peter at gigamonkeys.com (Peter Seibel) Date: Thu, 14 Dec 2006 08:56:17 -0800 Subject: [cl-pdf-devel] Big contibution committed In-Reply-To: <000001c71f70$d80edf40$8100a8c0@digo> References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> <00b201c71ea2$e20a4e90$1402a8c0@marcx2> <000701c71ee0$bdff9620$8100a8c0@digo> <000001c71f70$d80edf40$8100a8c0@digo> Message-ID: <88F7DCB5-4BB2-4C56-9A5F-369383527D61@gigamonkeys.com> On Dec 14, 2006, at 1:13 AM, Dmitriy Ivanov wrote: > "Attila Lendvai" wrote: > > | great! i've not noticed any regression on sbcl, but i still can't > | write unicode into pdf with typesetting. i get the utf-8 double > chars, > | even though i belive i've opened a bivalent stream with iso-8859-2 > | encoding (on sbcl). i'll further investigate this, but if somone > has a > | working unicode example it would be cool if it was committed into > the > | repo. > | > | and i also suggest to decide on an "official" lisp file encoding for > | the repo to avoid problems like you have with example8 (those chars > | decode to some chinese unicode chars when decoded in utf-8). i > suggest > | utf-8 for this, because that is the default at most places. > > utf-8 is hardly supported in PDF. I would suggest switching to UCS-2 > instead. For the source code (i.e. .lisp) files? I think that's what Attila was talking about. That seems a bit extreme as most of Lisp code is going to be ASCII. Unless I'm deeply misunderstanding something, the encoding we use for the Lisp code has nothing to do with what encoding we use to generate PDFs. No? -Peter From attila.lendvai at gmail.com Thu Dec 14 17:37:22 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Thu, 14 Dec 2006 18:37:22 +0100 Subject: [cl-pdf-devel] Big contibution committed In-Reply-To: <88F7DCB5-4BB2-4C56-9A5F-369383527D61@gigamonkeys.com> References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> <00b201c71ea2$e20a4e90$1402a8c0@marcx2> <000701c71ee0$bdff9620$8100a8c0@digo> <000001c71f70$d80edf40$8100a8c0@digo> <88F7DCB5-4BB2-4C56-9A5F-369383527D61@gigamonkeys.com> Message-ID: > For the source code (i.e. .lisp) files? I think that's what Attila > was talking about. That seems a bit extreme as most of Lisp code is > going to be ASCII. Unless I'm deeply misunderstanding something, the > encoding we use for the Lisp code has nothing to do with what > encoding we use to generate PDFs. No? that's right. i meant the lisp files, especially those that will contain unicode tests (you need to get some unicode text from somewhere that you write into the test pdf's). we could go by some (octets-to-string #(1 2 3 4 5)) expressions, but i think it's a lot simpler to agree that lisp files are utf-8 encoded. sbcl reads them as utf-8 by default, and i've got slime set up for that, too. for anyone looking for slime examples: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-wdim-environment;a=headblob;f=/init.el alternatively we can annotate: ;; -*- coding: utf-8 -*- but it's emacs only. this is a non-issue while there's no unicode test and now that Marc removed the non-ascii chars from the sources. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From divanov at aha.ru Thu Dec 14 17:42:49 2006 From: divanov at aha.ru (Dmitriy Ivanov) Date: Thu, 14 Dec 2006 20:42:49 +0300 Subject: [cl-pdf-devel] Big contibution committed References: <6F4E8149-42F6-4FE3-A107-D2427EFE3E58@gigamonkeys.com> <000001c71e8a$7633e0e0$8100a8c0@digo> <00b201c71ea2$e20a4e90$1402a8c0@marcx2> <000701c71ee0$bdff9620$8100a8c0@digo> <000001c71f70$d80edf40$8100a8c0@digo> <88F7DCB5-4BB2-4C56-9A5F-369383527D61@gigamonkeys.com> Message-ID: <000301c71fa7$4b56fce0$8100a8c0@digo> "Peter Seibel" wrote: | For the source code (i.e. .lisp) files? I think that's what Attila | was talking about. That seems a bit extreme as most of Lisp code is | going to be ASCII. Unless I'm deeply misunderstanding something, the | encoding we use for the Lisp code has nothing to do with what | encoding we use to generate PDFs. No? Yes, the encoding in a Lisp source file, a.g. examples.lisp, and the encoding instance in cal-pdf are different things. While reading this source file, different editors and various Lisp system readers make different assumptions about what its charset is. For example, plenty of strings in my Lisp code are in Windows-1251. In LispWorks memory, these strings are represented as UCS-2 strings, then they are converted back to Windows-1251-encoding and stored (compressed) in a PDF-file. -- Sincerely, Dmitriy Ivanov lisp.ystok.ru From jcm at FreeBSD-uk.eu.org Fri Dec 15 18:28:27 2006 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Fri, 15 Dec 2006 18:28:27 +0000 Subject: [cl-pdf-devel] Images and pdf size Message-ID: <20061215182826.GA28314@dogma.freebsd-uk.eu.org> Hi all, I'm having some problems with pdf file size after adding a logo png. I have a large one on the title page, and smaller ones on the additional pages. Is there a better way than add-images-to-page on each page? Can I add the png file to the document just once and then refer to it in each page as I need it? Jonathon McKitrick -- My other computer is your Windows box. From jcm at FreeBSD-uk.eu.org Sat Dec 16 14:29:00 2006 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Sat, 16 Dec 2006 14:29:00 +0000 Subject: [cl-pdf-devel] Image storage emergency Message-ID: <20061216142859.GA34863@dogma.freebsd-uk.eu.org> Hey guys, I'm having a bit of a crisis with images in pdf's. We have a logo on every page, and I'm not sure how to add the image only once to the document. The resulting pdf went from a few hundred K to 1.6M! I've got to get this resolved ASAP. Does anyone know how I can add a png to the pdf only once, then refer to it again on each page? Jonathon McKitrick -- My other computer is your Windows box. From dave at genworks.com Sat Dec 16 15:59:31 2006 From: dave at genworks.com (Dave Cooper) Date: Sat, 16 Dec 2006 10:59:31 -0500 Subject: [cl-pdf-devel] Image storage emergency In-Reply-To: <20061216142859.GA34863@dogma.freebsd-uk.eu.org> References: <20061216142859.GA34863@dogma.freebsd-uk.eu.org> Message-ID: <30eff3110612160759t71f2ce35g75cfe66d6b97068@mail.gmail.com> Jonathon: I think the answer to your question already there in your question :). Just add the image once to the document, _outside_ the scope of any of the pages. Here is a simple example (the image I am using is the jpeg image linked below but this should be the same with png images and make-png-image). With the example below, the resulting PDF file sizes are as follows (this is with pdf:*compress-streams* as nil): 1 page: 46404 5 pages: 48564 50 pages: 72921 500 pages: 318589 1000 pages: 593590 and if you inspect the PDF file you will see that the image stream data is only there once, near the beginning of the file, before any of the "<< /Type /Page" ;;;;;;;;;;;;; (defpackage :pdf-user (:use :cl :pdf)) (in-package :pdf-user) (defun logo-pages (&key (pages 50)) (pdf:with-document () (let ((logo-image (make-jpeg-image "/tmp/dj001.jpg"))) (dotimes (n pages) (with-page () (translate 30 700) (let ((helvetica (get-font "Helvetica"))) (in-text-mode (set-font helvetica 36.0) (draw-text (format nil "cl-pdf: Image Page ~a" n))) (add-images-to-page logo-image) (draw-image logo-image 0 -500 545 409 0 t))))) (write-document "/tmp/logo-pages.pdf"))) ;;;;;;;;;;; Here's the link to the sample image I used: http://f7.yahoofs.com/users/yVGXbR8p.DBo/__sr_/d2fa.jpg?tkn=phMKChFBFE1y15.x&saveas=dj001 -dave On 12/16/06, Jonathon McKitrick wrote: > Hey guys, > > I'm having a bit of a crisis with images in pdf's. We have a logo on every > page, and I'm not sure how to add the image only once to the document. The > resulting pdf went from a few hundred K to 1.6M! I've got to get this > resolved ASAP. Does anyone know how I can add a png to the pdf only once, > then refer to it again on each page? > > Jonathon McKitrick > -- > My other computer is your Windows box. > _______________________________________________ > cl-pdf-devel site list > cl-pdf-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/cl-pdf-devel > -- Dave Cooper dave at genworks.com 248-932-2166(o), 248-330-2979(c), 1-800-731-9220(toll-free in North America) From ungil at mac.com Sat Dec 16 18:46:04 2006 From: ungil at mac.com (Carlos Ungil) Date: Sat, 16 Dec 2006 19:46:04 +0100 Subject: [cl-pdf-devel] cl-pdf release 127 is broken (examples don't run on sbcl/macosx) Message-ID: <3EA7387A-1681-4FA1-B5FD-DDBF54CE2B5C@mac.com> Hello, I found a problem in release 127 and later (126 is ok). I'm using SBCL 1.0.34 on MacOSX/Intel and the examples result in the following error: # is not a character output stream. It seems to be related with the fragment :element-type #+pdf-binary '(unsigned-byte 8) #-pdf-binary 'base-char If I just comment those lines everything is ok until example #9 complains: # is not a binary output stream. Cheers, Carlos PS: By the way, thanks to all of you who have been recently applying patches. From jcm at FreeBSD-uk.eu.org Sat Dec 16 18:57:13 2006 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Sat, 16 Dec 2006 18:57:13 +0000 Subject: [cl-pdf-devel] Image storage emergency In-Reply-To: <30eff3110612160759t71f2ce35g75cfe66d6b97068@mail.gmail.com> References: <20061216142859.GA34863@dogma.freebsd-uk.eu.org> <30eff3110612160759t71f2ce35g75cfe66d6b97068@mail.gmail.com> Message-ID: <20061216185712.GA38682@dogma.freebsd-uk.eu.org> On Sat, Dec 16, 2006 at 10:59:31AM -0500, Dave Cooper wrote: : Jonathon: : : I think the answer to your question already there in your question :). : Just add the image once to the document, _outside_ the scope of any : of the pages. Thanks, you are a lifesaver! Call me an idiot, but I didn't think it would make a difference where you instantiate an image, if you still have to call add-images-to-page for every page. But fortunately, it's counter-intuitive in this case. I've just halved my pdf size, much to the relief of our CEO. Jonathon McKitrick -- My other computer is your Windows box. From dave at genworks.com Sat Dec 16 21:50:06 2006 From: dave at genworks.com (Dave Cooper) Date: Sat, 16 Dec 2006 16:50:06 -0500 Subject: [cl-pdf-devel] Image storage emergency In-Reply-To: <20061216185712.GA38682@dogma.freebsd-uk.eu.org> References: <20061216142859.GA34863@dogma.freebsd-uk.eu.org> <30eff3110612160759t71f2ce35g75cfe66d6b97068@mail.gmail.com> <20061216185712.GA38682@dogma.freebsd-uk.eu.org> Message-ID: <30eff3110612161350u251aa6b1g9e19ed64731f9730@mail.gmail.com> I should have said _make_ the image once, not so much _add_ . You're right, you still have to do add-images-to-page once for each page, but all that really does is to push an object reference and name onto a "dictionary" list for the page. -dave On 12/16/06, Jonathon McKitrick wrote: > On Sat, Dec 16, 2006 at 10:59:31AM -0500, Dave Cooper wrote: > : Jonathon: > : > : I think the answer to your question already there in your question :). > : Just add the image once to the document, _outside_ the scope of any > : of the pages. > > Thanks, you are a lifesaver! Call me an idiot, but I didn't think it would > make a difference where you instantiate an image, if you still have to call > add-images-to-page for every page. But fortunately, it's counter-intuitive in > this case. I've just halved my pdf size, much to the relief of our CEO. > > > Jonathon McKitrick > -- > My other computer is your Windows box. > -- Dave Cooper dave at genworks.com 248-932-2166(o), 248-330-2979(c), 1-800-731-9220(toll-free in North America) From divanov at aha.ru Mon Dec 18 08:13:47 2006 From: divanov at aha.ru (Dmitriy Ivanov) Date: Mon, 18 Dec 2006 11:13:47 +0300 Subject: [cl-pdf-devel] cl-pdf release 127 is broken (examples don't run onsbcl/macosx) References: <3EA7387A-1681-4FA1-B5FD-DDBF54CE2B5C@mac.com> Message-ID: <000001c7227c$75fde0d0$8100a8c0@digo> Hello Carlos, | Hello, | | I found a problem in release 127 and later (126 is ok). I'm using | SBCL 1.0.34 on MacOSX/Intel and the examples result in the following | error: | | # is not a | character output stream. | | It seems to be related with the fragment | | :element-type #+pdf-binary '(unsigned-byte 8) #-pdf-binary 'base-char | | If I just comment those lines everything is ok until example #9 | complains: | | # is not a | binary output stream. I am sorry. Aiming at the usage of binary pdf streams ubiquitously, I have (inadvertently :-)) replaced the initial interpretation of :pdf-binary with a stronger one "if your Lisp implementation accepts writing base characters to binary streams". This seems to be true for LispWorks only (maybe Allegro?). What do the others think? Does the rest of the code work? -- Sincerely, Dmitriy Ivanov lisp.ystok.ru From attila.lendvai at gmail.com Mon Dec 18 12:22:08 2006 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Mon, 18 Dec 2006 13:22:08 +0100 Subject: [cl-pdf-devel] cl-pdf release 127 is broken (examples don't run onsbcl/macosx) In-Reply-To: <000001c7227c$75fde0d0$8100a8c0@digo> References: <3EA7387A-1681-4FA1-B5FD-DDBF54CE2B5C@mac.com> <000001c7227c$75fde0d0$8100a8c0@digo> Message-ID: > "if your Lisp implementation accepts writing base characters to binary > streams". > > This seems to be true for LispWorks only (maybe Allegro?). What do the > others think? Does the rest of the code work? sbcl also supports bivalent streams if the :element-type is :default characters written into such streams are converted by the :external-format (which is utf-8 by default on unicode sbcl's) -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronst?llet) From jcm at FreeBSD-uk.eu.org Sat Dec 30 17:05:35 2006 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Sat, 30 Dec 2006 17:05:35 +0000 Subject: [cl-pdf-devel] Stream output error with cvs SBCL Message-ID: <20061230170535.GA62072@dogma.freebsd-uk.eu.org> I just grabbed a cvs SBCL since 1.0.1 came out, and I started to generate a pdf document. I got this error: The value 120 is not of type CHARACTER. [Condition of type TYPE-ERROR] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [TERMINATE-THREAD] Terminate this thread (#) Backtrace: 0: (SB-IMPL::OUTPUT-CHAR-LATIN-1-FULL-BUFFERED # 120) 1: (SB-IMPL::ANSI-STREAM-WRITE-SEQUENCE #(120 94 237 93 63 104 91 103 247 214 ...) # 0 NIL) 2: (WRITE-SEQUENCE #(120 94 237 93 63 104 91 103 247 214 ...) #) 3: ((SB-PCL::FAST-METHOD PDF::WRITE-OBJECT (PDF::PDF-STREAM)) # #S(SB-PCL::FAST-METHOD-CALL :FUNCTION # :PV-CELL NIL :NEXT-METHOD-CALL #S(SB-PCL::FAST-METHOD-CALL :FUNCTION # :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) :ARG-INFO (1 . T)) #) Locals: SB-PCL::.NEXT-METHOD-CALL. = #S(SB-PCL::FAST-METHOD-CALL :FUNCTION # :PV-CELL NIL :NEXT-METHOD-CALL #S(SB-PCL::FAST-METHOD-CALL :FUNCTION # :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) :ARG-INFO (1 . T)) SB-PCL::.REST-ARG. = NIL PDF::OBJ = # 4: ((SB-PCL::FAST-METHOD PDF::WRITE-OBJECT (PDF::INDIRECT-OBJECT)) # # # T) Is this an SBCL issue or a CL-PDF issue? Jonathon McKitrick -- My other computer is your Windows box. From marc.battyani at fractalconcept.com Sat Dec 30 21:31:14 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sat, 30 Dec 2006 22:31:14 +0100 Subject: [cl-pdf-devel] Stream output error with cvs SBCL References: <20061230170535.GA62072@dogma.freebsd-uk.eu.org> Message-ID: <054401c72c59$d8156220$1402a8c0@marcx2> "Jonathon McKitrick" wrote: > > I just grabbed a cvs SBCL since 1.0.1 came out, and I started to generate > a > pdf document. I got this error: [...] > Is this an SBCL issue or a CL-PDF issue? It's probably a cl-pdf issue. I think the latest patches from Dmitriy Ivanov don't work on SBCL. Maybe some SBCL user (Attila Lendvai?) can look at this? Marc From christopher.laux at web.de Sun Dec 31 21:27:25 2006 From: christopher.laux at web.de (Christopher Laux) Date: Sun, 31 Dec 2006 22:27:25 +0100 Subject: [cl-pdf-devel] Parsing pdf files Message-ID: <45982B3D.1020900@web.de> Hi all, I'm interested in parsing pdf files for, among other uses, rendering the text parts of them. I've seen the parser in pdf-parser.lisp, but if I'm not completely mistaken it only handles the meta-information such as pages and objects. To get the actual graphical content, i.e. lines and text, more work has to be done, right? I just wanted to make sure that I'm not duplicating functionality out of ignorance. And of course, if someone has some hints (or even code?) to offer, that would be great. Happy new year, Chris Laux From marc.battyani at fractalconcept.com Sun Dec 31 22:08:47 2006 From: marc.battyani at fractalconcept.com (Marc Battyani) Date: Sun, 31 Dec 2006 23:08:47 +0100 Subject: [cl-pdf-devel] Parsing pdf files References: <45982B3D.1020900@web.de> Message-ID: <00eb01c72d28$3f383b20$c800000a@marcxp> "Christopher Laux" wrote: > > I'm interested in parsing pdf files for, among other uses, rendering the > text parts of them. I've seen the parser in pdf-parser.lisp, but if I'm > not completely mistaken it only handles the meta-information such as > pages and objects. To get the actual graphical content, i.e. lines and > text, more work has to be done, right? It's more than just the meta information but yes the streams content are not parsed yet. Note that before parsing them, you need to decompress them if they are compressed (which is very likely). > I just wanted to make sure that I'm not duplicating functionality out of > ignorance. And of course, if someone has some hints (or even code?) to > offer, that would be great. I'm not aware about anybody else working on that. In general people just need to be able to write on pages or to get pages from another document. But this is interesting anyway. :) Marc