From: Alex R. <sh...@al...> - 2004-03-10 19:08:26
|
Hello everybody, The first draft of the gnome-print plugin written by Billy Earney and=20 myself is in CVS HEAD now. The following features are supported in the=20 direct printing/previewing: 1. Formatted text with the properties supplied by the report styles: font face, size, bold/italic attributes, alignment, and padding. 2. Tables (padding, cells spanning more than one column) 3. Images (this requires latest gnome-python: either CVS or=20 the Release Candidate for 2.2 available from http://www.gnome.org/~jdahlin/pygtk-2.2.0-RC1.tar.gz ) If supported, images should be properly placed in either text or into the table cells. 4. Superscripts, line breaks, boldface in parts of paragraph. 5. Graphic methods used in all GRAMPS' reports. 6. Book creation with any number of any items currently available. The text should appear without problem in any language, provided you=20 have either Freefont fonts or the Microsoft fonts installed. If you=20 have neither of those, everything should be fine for latin text, but=20 accented and other charsets (cyrillic, chinese, etc) will be garbled. Now, I am sure there's tons of rough spots which we did not encounter=20 yet. Therefore, I would very much like people to test this plugin and=20 report any strange behavior so that we can fix things before the=20 release. To get this plugin, download it from CVS at http://cvs.sourceforge.net/viewcvs.py/*checkout*/gramps/gramps2/src/docgen/= LPRDoc.py Then drop this file into your ~/.gramps/plugins directory and start=20 gramps. Use "Print..." as the format for the reports and then either=20 print it, create PS/PDF, or watch the preview. To report bugs, you may=20 create PDF with incorrect output and send it to me. PLEASE PLEASE PLEASE help testing the plugin! Note that this plugin is=20 installed locally, so it does not "contaminate" your stable gramps=20 installation in any way. At any time, you can move it away from your=20 ~/.gramps/plugins and it would not be loaded upon startup. Below is the list of issues I have yet to work on. You don't need to=20 report any of those, I know about them :-) 1. Formatted notes do not yet honor multiple spaces/tabs. 2. Book with AncestorChart and AncestorChart2 (Wall chart) mix up graphic styles. This is a bug in both reports, and is fixed in STABLE CVS branch. A result of these bugs is that the book with both charts will have the first one garbled. 3. Paper size is read afresh from gnomeprint config each time you start gramps. On one of my machines I get A4 while I would prefer US-Letter. Changing the size in the gnomeprint dialog=20 does not help this, because by the time this dialog is up the printing job is already laid out. The workaround would be=20 to select the desired paper and then say Cancel in gnome-print dialog. Then create the same report again, which will use=20 the correct paper size. 4. Photos are skipped unless the latest gnome-python is available, see above. Same about rotated text in Time Chart -- same reason. 5. FTMStyle Descendant report uses the same style for the small=20 roman numbers in the children table as it does for the main entry. The default style has large (1cm) margin so that the roman=20 numerals end up on the second line. This should be fixed by using different paragraph styles for these numerals. Thanks in advance for any feedback, Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Don A. <dal...@us...> - 2004-03-11 04:21:28
|
Alex and Billy, GREAT JOB! It has been a while since I gave the gnome-print interface a workout, and I have to say that I am really impressed at the progress. I ran through most of the reports, both graphical and text, and things look really good. Its really nice to be able to preview a document. Its much faster that trying to generate an OpenOffice document. To everyone else: Please give this a try. This resolves one of the biggest problems that GRAMPS has, and in my opinion, it is already usable. The more testing we can have, the better the quality will be. Don On Wed, 2004-03-10 at 11:58, Alex Roitman wrote: > > PLEASE PLEASE PLEASE help testing the plugin! Note that this plugin is > installed locally, so it does not "contaminate" your stable gramps > installation in any way. At any time, you can move it away from your > ~/.gramps/plugins and it would not be loaded upon startup. > > Below is the list of issues I have yet to work on. You don't need to > report any of those, I know about them :-) > > 1. Formatted notes do not yet honor multiple spaces/tabs. > 2. Book with AncestorChart and AncestorChart2 (Wall chart) > mix up graphic styles. This is a bug in both reports, and is > fixed in STABLE CVS branch. A result of these bugs is that > the book with both charts will have the first one garbled. > 3. Paper size is read afresh from gnomeprint config each time > you start gramps. On one of my machines I get A4 while I would > prefer US-Letter. Changing the size in the gnomeprint dialog > does not help this, because by the time this dialog is up > the printing job is already laid out. The workaround would be > to select the desired paper and then say Cancel in gnome-print > dialog. Then create the same report again, which will use > the correct paper size. > 4. Photos are skipped unless the latest gnome-python is available, > see above. Same about rotated text in Time Chart -- same reason. Did you mean Fan Chart? > 5. FTMStyle Descendant report uses the same style for the small > roman numbers in the children table as it does for the main entry. > The default style has large (1cm) margin so that the roman > numerals end up on the second line. This should be fixed by using > different paragraph styles for these numerals. > > Thanks in advance for any feedback, > Alex -- Don Allingham <dal...@us...> GRAMPS - Open Source Genealogy |
From: Alex R. <sh...@al...> - 2004-03-12 18:00:13
|
Has anybody had a chance to try out the LPRDoc.py plugin? I'm anxious to get some feedback, please send me some :-) If you have tried it and it works for you, please say so :-) For those who missed the previous call, the details are below. Thanks, Alex On 03/10/2004 12:58:34 PM, Alex Roitman wrote: >=20 > The first draft of the gnome-print plugin written by Billy Earney and > myself is in CVS HEAD now. The following features are supported in=20 > the >=20 > direct printing/previewing: >=20 > 1. Formatted text with the properties supplied by the report styles: > font face, size, bold/italic attributes, alignment, and padding. > 2. Tables (padding, cells spanning more than one column) > 3. Images (this requires latest gnome-python) > If supported, images should be properly placed in either text > or into the table cells. > 4. Superscripts, line breaks, boldface in parts of paragraph. > 5. Graphic methods used in all GRAMPS' reports. > 6. Book creation with any number of any items currently available. >=20 > The text should appear without problem in any language, provided you > have either Freefont fonts or the Microsoft fonts installed. If you > have neither of those, everything should be fine for latin text, but > accented and other charsets (cyrillic, chinese, etc) will be garbled. >=20 > Now, I am sure there's tons of rough spots which we did not encounter > yet. Therefore, I would very much like people to test this plugin and > report any strange behavior so that we can fix things before the > release. >=20 > To get this plugin, download it from CVS at > http://cvs.sourceforge.net/viewcvs.py/*checkout*/gramps/gramps2/src/docge= n/LPRDoc.py >=20 > Then drop this file into your ~/.gramps/plugins directory and start > gramps. Use "Print..." as the format for the reports and then either > print it, create PS/PDF, or watch the preview. To report bugs, you=20 > may create PDF with incorrect output and send it to me. >=20 > PLEASE PLEASE PLEASE help testing the plugin! Note that this plugin=20 > is installed locally, so it does not "contaminate" your stable gramps > installation in any way. At any time, you can move it away from your > ~/.gramps/plugins and it would not be loaded upon startup. >=20 > Below is the list of issues I have yet to work on. You don't need to > report any of those, I know about them :-) >=20 > 1. Formatted notes do not yet honor multiple spaces/tabs. > 2. Book with AncestorChart and AncestorChart2 (Wall chart) > mix up graphic styles. This is a bug in both reports, and is > fixed in STABLE CVS branch. A result of these bugs is that > the book with both charts will have the first one garbled. > 3. Paper size is read afresh from gnomeprint config each time > you start gramps. On one of my machines I get A4 while I would > prefer US-Letter. Changing the size in the gnomeprint dialog > does not help this, because by the time this dialog is up > the printing job is already laid out. The workaround would be > to select the desired paper and then say Cancel in gnome-print > dialog. Then create the same report again, which will use > the correct paper size. > 4. Photos are skipped unless the latest gnome-python is available, > see above. Same about rotated text in Time Chart -- same reason. > 5. FTMStyle Descendant report uses the same style for the small > roman numbers in the children table as it does for the main > entry. The default style has large (1cm) margin so that the roman > numerals end up on the second line. This should be fixed by using > different paragraph styles for these numerals. >=20 > Thanks in advance for any feedback, > Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-13 01:17:25
|
fre, 12.03.2004 kl. 18.49 skrev Alex Roitman: > Has anybody had a chance to try out the LPRDoc.py plugin? > I'm anxious to get some feedback, please send me some :-) > > If you have tried it and it works for you, please say so :-) Hmm. I just tried it very briefly. It seems to work well, but if I try to make a PDF in A0 size, it can't be done. It looks like gnome-print only wants to use the available paper sizes from a selected printer. If so, I guess that's a problem with gnome-print and not the plugin? Anyway, great work! Best regards, Stian |
From: Alex R. <sh...@al...> - 2004-03-13 01:29:00
|
Stian, On Sat, Mar 13, 2004 at 02:16:30AM +0100, Stian Jordet wrote: > fre, 12.03.2004 kl. 18.49 skrev Alex Roitman: > > Has anybody had a chance to try out the LPRDoc.py plugin? > > I'm anxious to get some feedback, please send me some :-) > >=20 > > If you have tried it and it works for you, please say so :-) >=20 > Hmm. I just tried it very briefly. It seems to work well, but if I try > to make a PDF in A0 size, it can't be done. It looks like gnome-print > only wants to use the available paper sizes from a selected printer. If > so, I guess that's a problem with gnome-print and not the plugin? I am trying to figure out the gnome-print quirks at the moment (and I have to tell you -- there's plenty :-) relating to proper paper size settings. It is my (so far unconfirmed) impression that each backend (PDF, Generic Postscript, CUPS system, and whatever else can work as a printing backend) has its own set of available paper sizes within gnomeprint. The selection list available for PDF is rather scarce, as you have noticed. I don't know yet whether it is possible to set PDF paper size to A0 in any way. It seems that it is possible with Generic postsrcipt backend. I would imagine that ps2pdf or xpdf-related tools can convert such a=20 postscript to PDF.=20 If anybody has insights into the dark inner workings of gnome-print,=20 please don't hesitate to enlighten us mortals :-) Thanks, Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-16 01:54:29
|
l=F8r, 13.03.2004 kl. 02.28 skrev Alex Roitman: > Stian, >=20 > On Sat, Mar 13, 2004 at 02:16:30AM +0100, Stian Jordet wrote: > > fre, 12.03.2004 kl. 18.49 skrev Alex Roitman: > > > Has anybody had a chance to try out the LPRDoc.py plugin? > > > I'm anxious to get some feedback, please send me some :-) > > >=20 > > > If you have tried it and it works for you, please say so :-) > >=20 > > Hmm. I just tried it very briefly. It seems to work well, but if I tr= y > > to make a PDF in A0 size, it can't be done. It looks like gnome-print > > only wants to use the available paper sizes from a selected printer. = If > > so, I guess that's a problem with gnome-print and not the plugin? >=20 > I am trying to figure out the gnome-print quirks at the moment (and > I have to tell you -- there's plenty :-) relating to proper paper size > settings. > > It is my (so far unconfirmed) impression that each backend (PDF, Generi= c > Postscript, CUPS system, and whatever else can work as a printing backe= nd) > has its own set of available paper sizes within gnomeprint. The selecti= on > list available for PDF is rather scarce, as you have noticed. >=20 > I don't know yet whether it is possible to set PDF paper size to A0 > in any way. It seems that it is possible with Generic postsrcipt backen= d. > I would imagine that ps2pdf or xpdf-related tools can convert such a=20 > postscript to PDF.=20 I tried using ps2pdf, but that gave a very, very unexpected result. The ancestor chart was suddenly using greek characters (or something that looked like it), besides the chart was clipped, and was obviously not A0, even if I could choose that paper size. As I said, I understand that it is a Gnome bug that you can't make larger pdf's than A0 (or Letter), but should I file a bugreport at their bugzilla about it? And when talking about bugs... The ancestor chart pdf-report is now capable of creating files with the norwegian characters =E6=F8=E5. But th= e fan chart is not, for some reason. Except for me being unable to create A0 pdf's, the Gnome-print plugin works very good :) I do have one idea for a new feature, but I'm not sure you like it. Now one can scale charts to fit on one page. This is a very good feature, which Don actually made to satisfy me :) Problem is, that I can write a 10 generation chart to a A4 page, and it will be way to small to read. But if I select to not scale it, it actually becomes 100 pages, which is way to much. I would guess that 5-10 pages would have been enough to be able to read it. What I would love is an option to select how many pages it should fit on, not just one. Is this just crazy? Thanks for your always prompt response, and kind help, and sorry for always being so demanding without giving anything back. Best regards, Stian |
From: Alex R. <sh...@al...> - 2004-03-16 02:13:48
|
On Tue, Mar 16, 2004 at 02:53:33AM +0100, Stian Jordet wrote: >=20 > I tried using ps2pdf, but that gave a very, very unexpected result. The > ancestor chart was suddenly using greek characters (or something that > looked like it), besides the chart was clipped, and was obviously not > A0, even if I could choose that paper size. Oops :-) If that does not work then I don't know, sorry :-( I guess that ps2pdf wants to replace the fonts with the built-in postscript fonts (Times, Helvetica, and Courier) which do not cover Unicode Character Set (UCS). Did the postscript created by gnome-print look OK? Maybe you can get by with PS files for that size? I know it's a lame excuse, but I don't know the good solution for this problem :-) > As I said, I understand that it is a Gnome bug that you can't make > larger pdf's than A0 (or Letter), but should I file a bugreport at their > bugzilla about it? Maybe it's a good idea. I posted my questions to both pygtk and gnome-print lists and got no answer. At least, whoever will close that bug might be able to explain how to do it :-) Could you please let me know the bug number after you file it? > And when talking about bugs... The ancestor chart pdf-report is now > capable of creating files with the norwegian characters =E6=F8=E5. But th= e fan > chart is not, for some reason. Unless you have CVS version of gnome-python, fan chart should appear without any text at all, no matter what the characters are. This is because=20 fan chart needs to use rotated text, and this (as well as adding photos) requires CVS gnome-python. As soon as the new gnome-python is released,=20 the fan chart should start working automatically.=20 > ... I do have one idea for a new feature, but I'm not > sure you like it. Now one can scale charts to fit on one page. This is a > very good feature, which Don actually made to satisfy me :) Problem is, > that I can write a 10 generation chart to a A4 page, and it will be way > to small to read. But if I select to not scale it, it actually becomes > 100 pages, which is way to much. I would guess that 5-10 pages would > have been enough to be able to read it. What I would love is an option > to select how many pages it should fit on, not just one. Is this just > crazy? I think not :-) But I'm not familiar with that code. I think it's a question for Don. Thanks for your feedback, Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-16 02:34:00
|
tir, 16.03.2004 kl. 03.13 skrev Alex Roitman: > > And when talking about bugs... The ancestor chart pdf-report is now > > capable of creating files with the norwegian characters =E6=F8=E5. Bu= t the fan > > chart is not, for some reason. >=20 > Unless you have CVS version of gnome-python, fan chart should appear wi= thout > any text at all, no matter what the characters are. This is because=20 > fan chart needs to use rotated text, and this (as well as adding photos= ) > requires CVS gnome-python. As soon as the new gnome-python is released,= =20 > the fan chart should start working automatically.=20 I was actually talking about pdf's made by reportlab :) Best regards, Stian |
From: Alex R. <sh...@al...> - 2004-03-16 02:53:47
|
Stian, On Tue, Mar 16, 2004 at 03:33:08AM +0100, Stian Jordet wrote: > tir, 16.03.2004 kl. 03.13 skrev Alex Roitman: > > > And when talking about bugs... The ancestor chart pdf-report is now > > > capable of creating files with the norwegian characters =E6=F8=E5. Bu= t the fan > > > chart is not, for some reason. > >=20 > > Unless you have CVS version of gnome-python, fan chart should appear wi= thout > > any text at all, no matter what the characters are. This is because=20 > > fan chart needs to use rotated text, and this (as well as adding photos) > > requires CVS gnome-python. As soon as the new gnome-python is released,= =20 > > the fan chart should start working automatically.=20 >=20 > I was actually talking about pdf's made by reportlab :) You lost me here :-) The reportlab should not be able to display unicode chars. I might be wrong, but it should be the same behavior across all reports. Unless you compared reportlab's fan chart with gnome-print's ancestor chart, which could explain it :-) Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-16 03:03:48
|
tir, 16.03.2004 kl. 03.53 skrev Alex Roitman: > Stian, >=20 > On Tue, Mar 16, 2004 at 03:33:08AM +0100, Stian Jordet wrote: > > tir, 16.03.2004 kl. 03.13 skrev Alex Roitman: > > > > And when talking about bugs... The ancestor chart pdf-report is n= ow > > > > capable of creating files with the norwegian characters =E6=F8=E5= . But the fan > > > > chart is not, for some reason. > > >=20 > > > Unless you have CVS version of gnome-python, fan chart should appea= r without > > > any text at all, no matter what the characters are. This is because= =20 > > > fan chart needs to use rotated text, and this (as well as adding ph= otos) > > > requires CVS gnome-python. As soon as the new gnome-python is relea= sed,=20 > > > the fan chart should start working automatically.=20 > >=20 > > I was actually talking about pdf's made by reportlab :) >=20 > You lost me here :-) The reportlab should not be able to display unicod= e > chars. I might be wrong, but it should be the same behavior across all > reports. >=20 > Unless you compared reportlab's fan chart with gnome-print's ancestor > chart, which could explain it :-) Nope, I'm 100% positive, I'm using reportlab for both charts :) And the ancestor chart displays =E6=F8=E5 correctly (it did not in the past (0.98= , at least)), but it sure does now, I can mail you a sample if you don't believe me :) The fan chart does not display =E6=F8=E5. And I have no idea why.=20 Best regards, Stian |
From: Alex R. <sh...@al...> - 2004-03-16 03:10:59
|
On Tue, Mar 16, 2004 at 04:02:54AM +0100, Stian Jordet wrote: >=20 > Nope, I'm 100% positive, I'm using reportlab for both charts :) And the > ancestor chart displays =E6=F8=E5 correctly (it did not in the past (0.98= , at > least)), but it sure does now, I can mail you a sample if you don't > believe me :) I believe you. There must be some explicit conversion to latin in the Fan Chart then... There it is: the pdf generator (which interfaces with the reportlab) has str(line) statement in the rotated text method, which converts text to ascii. Just curious: if you change "str(line)" to simply "line" in line 496 of src/docgen/PdfDoc.py (or /usr/share/gramps/docgen/PdfDoc.py if you use packaged gramps), does it help? Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-16 03:21:55
|
tir, 16.03.2004 kl. 04.10 skrev Alex Roitman: > On Tue, Mar 16, 2004 at 04:02:54AM +0100, Stian Jordet wrote: > >=20 > > Nope, I'm 100% positive, I'm using reportlab for both charts :) And t= he > > ancestor chart displays =E6=F8=E5 correctly (it did not in the past (= 0.98, at > > least)), but it sure does now, I can mail you a sample if you don't > > believe me :) >=20 > I believe you. There must be some explicit conversion to latin in > the Fan Chart then... >=20 > There it is: the pdf generator (which interfaces with the reportlab) > has str(line) statement in the rotated text method, which converts text > to ascii. >=20 > Just curious: if you change "str(line)" to simply "line" in line 496 > of src/docgen/PdfDoc.py (or /usr/share/gramps/docgen/PdfDoc.py if you > use packaged gramps), does it help? Not even close :) GRAMPS : 1.0.1-1 LANG : no_NO Python : 2.3.3 final GTK : 2.2.4 PyGTK : 2.2.0 Traceback (most recent call last): File "/usr/share/gramps/plugins/FanChart.py", line 340, in make_report MyReport.write_report() File "/usr/share/gramps/plugins/FanChart.py", line 189, in write_report self.circle_5(center,y,block_size) File "/usr/share/gramps/plugins/FanChart.py", line 267, in circle_5 xc,yc ,sangle) File "/usr/share/gramps/docgen/PdfDoc.py", line 501, in rotate_text textAnchor=3D'middle') File "/usr/lib/python2.3/site-packages/reportlab/graphics/shapes.py", line 1186, in __init__ self.text =3D text File "/usr/lib/python2.3/site-packages/reportlab/graphics/shapes.py", line 304, in __setattr__ validateSetattr(self,attr,value) #from reportlab.lib.attrmap File "/usr/lib/python2.3/site-packages/reportlab/lib/attrmap.py", line 81, in validateSetattr raise AttributeError, "Illegal assignment of '%s' to '%s' in class %s" % (value, name, obj.__class__.__name__) AttributeError: Illegal assignment of 'Edvard' to 'text' in class String Best regards, Stian |
From: Alex R. <sh...@al...> - 2004-03-16 03:38:24
|
Stian,=20 I guess I was not all that lucky with my guess :-) Sorry, let's wait for the new gnome-python release and use OOo workaround= =20 in the meantime. If you feel like installing CVS version of gnome-python then gnome-print plugin should be able to print the Fan Chart properly, with whatever characters. Otherwise, we're all at the mercy of a few brave individuals trying to push gnome-python out :-) Alex On Tue, Mar 16, 2004 at 04:21:02AM +0100, Stian Jordet wrote: > tir, 16.03.2004 kl. 04.10 skrev Alex Roitman: > >=20 > > Just curious: if you change "str(line)" to simply "line" in line 496 > > of src/docgen/PdfDoc.py (or /usr/share/gramps/docgen/PdfDoc.py if you > > use packaged gramps), does it help? >=20 > Not even close :) >=20 > GRAMPS : 1.0.1-1 > LANG : no_NO > Python : 2.3.3 final > GTK : 2.2.4 > PyGTK : 2.2.0 > Traceback (most recent call last): --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Alex R. <sh...@al...> - 2004-03-16 04:37:07
|
Stian, I think I've found the answer. Change "str(line)" to "enc(line)" on line 496, and also change "str(text)" to "enc(text)" on lines 457 and 463 in the same file (PdfDoc.py). Sorry for the brain-dead advice I gave you before :-) Alex On Tue, Mar 16, 2004 at 04:21:02AM +0100, Stian Jordet wrote: > > Just curious: if you change "str(line)" to simply "line" in line 496 > > of src/docgen/PdfDoc.py (or /usr/share/gramps/docgen/PdfDoc.py if you > > use packaged gramps), does it help? >=20 > Not even close :) --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-16 11:53:56
|
tir, 16.03.2004 kl. 05.36 skrev Alex Roitman: > Stian, > > I think I've found the answer. Change "str(line)" to "enc(line)" on > line 496, and also change "str(text)" to "enc(text)" on lines 457 and 463 > in the same file (PdfDoc.py). > > Sorry for the brain-dead advice I gave you before :-) Yep, that fixed it :) It was not very important, since I can use the gnome-print plugin with updated gnome-python. The OOo workaround is ugly, it makes way uglier charts. But now there is no problem with the reportlab pdf's for me. This makes it a less problem for me that I can't make A0 pdf's with gnome-print. Will file bug later today, btw. Great work again, thanks :) Will this fix be commited, or does it cause a regression for something else? Best regards, Stian |
From: Alex R. <sh...@al...> - 2004-03-16 15:31:47
|
On Tue, Mar 16, 2004 at 12:52:50PM +0100, Stian Jordet wrote: > >=20 > > I think I've found the answer. Change "str(line)" to "enc(line)" on > > line 496, and also change "str(text)" to "enc(text)" on lines 457 and 4= 63 > > in the same file (PdfDoc.py). > >=20 > > Sorry for the brain-dead advice I gave you before :-) >=20 > Yep, that fixed it :) It was not very important, since I can use the > gnome-print plugin with updated gnome-python. The OOo workaround is > ugly, it makes way uglier charts. But now there is no problem with the > reportlab pdf's for me. This makes it a less problem for me that I can't > make A0 pdf's with gnome-print. Will file bug later today, btw. Hold on a little bit. I just got response from gnome-devel-list so I might figure something in that area.=20 > Great work again, thanks :) Will this fix be commited, or does it cause > a regression for something else? It is in CVS and will appear in the next release. Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Stian J. <li...@jo...> - 2004-03-16 15:15:36
|
tir, 16.03.2004 kl. 03.13 skrev Alex Roitman: > > As I said, I understand that it is a Gnome bug that you can't make > > larger pdf's than A0 (or Letter), but should I file a bugreport at their > > bugzilla about it? > > Maybe it's a good idea. I posted my questions to both pygtk and gnome-print > lists and got no answer. At least, whoever will close that bug might be > able to explain how to do it :-) Could you please let me know the bug number > after you file it? http://bugzilla.gnome.org/show_bug.cgi?id=137376 Best regards, Stian |
From: Egyeki G. <eg...@el...> - 2004-03-15 20:16:07
|
On Fri, 12 Mar 2004, Alex Roitman wrote: > Has anybody had a chance to try out the LPRDoc.py plugin? > I'm anxious to get some feedback, please send me some :-) > > If you have tried it and it works for you, please say so :-) > > For those who missed the previous call, the details are below. > > Thanks, > Alex Alex and Billy, This is great! For me work fine! Geri |
From: James A. T. <tr...@de...> - 2004-03-12 22:01:27
|
On Wed, Mar 10, 2004 at 12:58:34PM -0600, Alex Roitman wrote: > > To get this plugin, download it from CVS at > http://cvs.sourceforge.net/viewcvs.py/*checkout*/gramps/gramps2/src/docgen/LPRDoc.py > > Then drop this file into your ~/.gramps/plugins directory and start > gramps. Use "Print..." as the format for the reports and then either > print it, create PS/PDF, or watch the preview. To report bugs, you may > create PDF with incorrect output and send it to me. Can this be tested from 1.0.1? I moved the file to the plugins dir (mode 644) but none of the reports I tried had "Print..." as an option for the Output Format. Am I doing something wrong? -- James (Jay) Treacy tr...@de... |
From: Alex R. <sh...@al...> - 2004-03-12 22:11:38
|
On 03/12/2004 03:50:13 PM, James A. Treacy wrote: > On Wed, Mar 10, 2004 at 12:58:34PM -0600, Alex Roitman wrote: > > > > To get this plugin, download it from CVS at > > =20 > http://cvs.sourceforge.net/viewcvs.py/*checkout*/gramps/gramps2/src/docge= n/LPRDoc.py > > >> Then drop this file into your ~/.gramps/plugins directory and start =20 >> gramps. Use "Print..." as the format for the reports and then =20 >> either print it, create PS/PDF, or watch the preview. To report =20 >> bugs, you may create PDF with incorrect output and send it to me. >=20 > Can this be tested from 1.0.1? Yes. > I moved the file to the plugins dir (mode 644) but none of the =20 > reports I tried had "Print..." as an option for the Output Format. Strange. Works fine for me with gramps 1.0.1-1 from debian unstable. It =20 should even work with much older gramps, it's not specific to the core =20 at all. What do you see if you select Help->Show plugin status...? > Am I doing something wrong? Not unless you mistakenly put your plugin into some directory other =20 than ~/.gramps/plugins dir. Let me know what the plugin status shows. Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Ted A. <tj...@po...> - 2004-03-12 23:32:37
|
Sorry, I accidentally moved this off the list by not replying to all... On Sat, 2004-03-13 at 00:18, Alex Roitman wrote: > Ted, > > On 03/12/2004 05:11:22 PM, Ted Anderson wrote: > > On Fri, 2004-03-12 at 23:57, Alex Roitman wrote: > >> If you get the same ImportError then gnome-python (or gnomeprint > >> portion of that) is not installed on your system. What distro are > >> you running? > > > > I'm running MDK 9.2, and I did need to install the gnome-python- > > gnomeprint package. I just did that, and now it seems I can use the > > plugin. > > Super!!! Could you please send the link to the package you had to > install to gra...@li... -- I already had another person > with the same problem under Mandrake. I installed the package from the contrib library through urpmi, but it's also available at: http://fr2.rpmfind.net//linux/RPM/mandrake/9.2/contrib/i586/gnome-python-gnomeprint-2.0.0-2mdk.i586.html > > > However, when I select print to PDF, no file seems to be created. I > > have been very specific with the filename to include the complete > > directory, but I can't find the PDF file anywhere on my system after > > saying print. > > Didn't you use the browse button to specify the filename? Any messages > in your terminal? Can you create PDF from other Gnome applications > (like gedit or abiword)? I can make PDF files with no problem. There seems to be a bug in my gnomeprint, because no matter what filename I select in the gnomeprint dialog (the gramps browse button is irrelevant here), the file is saved as output.pdf in my home directory. I tried this with Evolution as well and got the same results. So, I can say that the plugin seems to work fine; it's gnomeprint that needs some troubleshooting now. > > > The print preview seems to work fine. > > Good! -- Ted |
From: Alex R. <sh...@al...> - 2004-03-12 23:50:58
|
Ted, On 03/12/2004 05:30:47 PM, Ted Anderson wrote: > I installed the package from the contrib library through urpmi, but > it's also available at: >=20 > http://fr2.rpmfind.net//linux/RPM/mandrake/9.2/contrib/i586/gnome-python-= gnomeprint-2.0.0-2mdk.i586.html Thanks for the reference. I found the same thing :-) > I can make PDF files with no problem. There seems to be a bug in my =20 > gnomeprint, because no matter what filename I select in the =20 > gnomeprint dialog (the gramps browse button is irrelevant here), the =20 > file is saved as output.pdf in my home directory. For the record, I didn't mean the gramps browse button. On my machine, =20 the file selection in gnomeprint dialog is made with its own browse =20 button and there's no text entry field at all -- that's why I asked =20 about the button :-) > I tried this with Evolution as well and got the same results. So, =20 > I can say that the plugin seems to work fine; it's gnomeprint that =20 > needs some troubleshooting now. I know that the recent release of gnome-python is incomplete, so I =20 would not be surprised to find that it is buggy. Hopefully, the new =20 gnome-python will be released soon which will fix both this problem and =20 also enable adding images and rotating text. Mandrake 9.2 users: does anybody know if there's a fix for this problem =20 by any chance? Alex --=20 Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Ted A. <tj...@po...> - 2004-03-13 00:12:09
Attachments:
gnomeprint.png
|
On Sat, 2004-03-13 at 00:50, Alex Roitman wrote: > > I can make PDF files with no problem. There seems to be a bug in my > > gnomeprint, because no matter what filename I select in the > > gnomeprint dialog (the gramps browse button is irrelevant here), the > > file is saved as output.pdf in my home directory. > > For the record, I didn't mean the gramps browse button. On my machine, > the file selection in gnomeprint dialog is made with its own browse > button and there's no text entry field at all -- that's why I asked > about the button :-) Attached is my gnomeprint dialog on MDK 9.2...now that I know there's a problem I'll try to find the answer on MDK/Gnome/Ximian sites... |
From: Alex R. <sh...@al...> - 2004-03-13 00:29:15
Attachments:
alex_gnomeprint.png
|
On 03/12/2004 06:05:37 PM, Ted Anderson wrote: > Attached is my gnomeprint dialog on MDK 9.2...now that I know there's > a problem I'll try to find the answer on MDK/Gnome/Ximian sites... Here's mine, in case it helps tracking it down. I run debian unstable. Alex -- Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Charles R. D. <de...@ro...> - 2004-03-13 16:33:03
|
Alex Roitman wrote: > To get this plugin, download it from CVS at > http://cvs.sourceforge.net/viewcvs.py/*checkout*/gramps/gramps2/src/docgen/LPRDoc.py > > Then drop this file into your ~/.gramps/plugins directory and start > gramps. Use "Print..." as the format for the reports and then either > print it, create PS/PDF, or watch the preview. To report bugs, you may > create PDF with incorrect output and send it to me. Hi, I just started using gramps a couple of weeks ago. I saw the notice about a new print plugin and thought I'd try it. I'm missing something. When I do the Help->Show plugin status I get the following: ------------------------------------------------------------- The following modules could not be loaded: PdfDoc.py: The ReportLab modules are not installed RelGraph.py: ImportError Traceback (most recent call last): File "/usr/share/gramps/Plugins.py", line 388, in load_plugins a = __import__(plugin) File "/usr/share/gramps/plugins/RelGraph.py", line 34, in ? from sets import Set ImportError: No module named sets LPRDoc.py: ImportError Traceback (most recent call last): File "/usr/share/gramps/Plugins.py", line 388, in load_plugins a = __import__(plugin) File "/home/charlie/.gramps/plugins/LPRDoc.py", line 45, in ? import gnomeprint, gnomeprint.ui ImportError: No module named gnomeprint ---------------------------------------------------------------- There are actually 3 errors here the last of which involves the new plugin. Seems like I'm missing ReportLab, a module called sets and a module called gnomeprint. I'm running RH9 and useing KDE as a desktop. I ran the native RH package management gui and did not see any of these in there. I also have synaptic (gui for apt-get) and I didn't see them there, either. I found information about ReportLab on the gramps.sourceforge.net installation page. But what about the others? Are they part of some other rpm (or more than one rpm)? If so, what do I need to load? Thanks for any pointers. Charlie http://www.dennett.org/genealogy |