[Gramps-devel] Re: call for help with testing the gnome-print plugin

[Alex R. <sh...@al...>]

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