From: Eero T. <eer...@ne...> - 2005-08-18 18:55:46
Attachments:
gramps-oo-output.png
|
Hi, On Monday 08 August 2005 19:03, Alex Roitman wrote: > Again, we decided to do it for all reports, but after 2.0.6. The new > progress bar interface is simple, see Utils.ProgressMeter() class for > details. Also see e.g. src/plugins/Check.py for the example use. > > > The typical use is this: > ----------------------------------------------------- > import Utils # already done in all reports, I think > > progress = Utils.ProgressMeter(_('Overall title'),_('Pass title')='') > > progress.set_pass(_('First pass title'),number_of_total_steps) > progress.step() > > progress.set_pass(_('Second pass title'),number_of_total_steps) > progress.step() > > progress.close() > ----------------------------------------------------- Now that 2.0.6 is released, I've added support for this to the Statistics chart. Additionally I made all the barchart texts left aligned in (vain) hope that this would fix the report issues with Gramps font metrics problems, and included the number of persons to each legend item in hope that this clarifies the meaning the charts. I made also several changes to it which require localization changes: - Added the progress meter titles - Added title option for the ReportUtils.draw_legend() and used it with the Statistic Charts - Changed all the StatisticsChart chart type names to singular form (and changed the chart selection tab to say "Charts" instead). This way I could reuse these as legend headings Additionally I added context to "Title" strings in several other files. (This is for Finnish, unfortunately the main problem for this is the glade file containing Edit person dialog where I cannot use localization context. :-/) I haven't updated the template.po yet as I'm assuming that making rest of the reports to use progress indicators will need this too. Bug: There seems to be some problem with Gramps PostScript generation. I get this error from the GhostScript on the Gramps generated PostScript file: ---------- gs ~/statistics_chart.ps ESP Ghostscript 7.07 (2003-07-12) Copyright 2003 artofcode LLC and Easy Software Products, all rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Error: /undefined in 0,0000 Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1057/1417(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)-- Current allocation mode is local Current file position is 612 ESP Ghostscript 7.07.1: Unrecoverable error, exit code 1 ----------- When looking at the file with less, it looks quite normal PS i.e. the file contents are in right format and not (as far as I could see) e.g. truncated. The generated OO and PDF files worked OK in Xpdf and OO, except that there seems to be some problems (again) with OO output, see the attached OO screenshot: - legend and pie outlines are missing - legend texts are position wierdly (My OpenOffice is 1.1.1 version from SUSE 9.1.) - Eero |
From: Eero T. <eer...@ne...> - 2005-09-25 18:04:43
Attachments:
stat-generic.png
|
Hi, On Sunday 25 September 2005 20:23, Alex Roitman wrote: > Sorry for the belated followup on this. > > On Thu, 2005-08-18 at 02:07 +0300, Eero Tamminen wrote: > > Bug: > > There seems to be some problem with Gramps PostScript generation. > > I get this error from the GhostScript on the Gramps generated > > PostScript file: > > ---------- > > gs ~/statistics_chart.ps > > ESP Ghostscript 7.07 (2003-07-12) > > Copyright 2003 artofcode LLC and Easy Software Products, all rights > > reserved. > > This software comes with NO WARRANTY: see the file COPYING for details. > > Error: /undefined in 0,0000 > > Operand stack: > > > > Execution stack: > > %interp_exit .runexec2 --nostringval-- --nostringval-- > > --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- > > --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 > > 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- > > --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- > > --nostringval-- --nostringval-- > > Dictionary stack: > > --dict:1057/1417(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)-- > > Current allocation mode is local > > Current file position is 612 > > ESP Ghostscript 7.07.1: Unrecoverable error, exit code 1 > > ----------- > > > > When looking at the file with less, it looks quite normal PS i.e. the > > file contents are in right format and not (as far as I could see) e.g. > > truncated. > > Is this still an issue? If so, could you please send me the PS file Here: http://www.netsonic.fi/~vellam12/bin/statistics_chart.ps.gz > and the recipe of reproducing it? If possible, with the example > database. Note that this problem doesn't exist with English version of the report. Test-case: - Start Gramps with LANG=fi_FI.utf-8 - Open example database - Select "Raportit" -> "Graafiset raportit" -> "Tilastokaaviot..." - Select options show in attached screenshot - On the second tab, select all checkboxes - Click OK - Eero |
From: Alex R. <sh...@gr...> - 2005-09-25 19:14:51
|
Eero, On Sun, 2005-09-25 at 21:23 +0300, Eero Tamminen wrote: > > Is this still an issue? If so, could you please send me the PS file >=20 > Here: > http://www.netsonic.fi/~vellam12/bin/statistics_chart.ps.gz It does look broken. > > and the recipe of reproducing it? If possible, with the example > > database. >=20 > Note that this problem doesn't exist with English version of the report. >=20 > Test-case: > - Start Gramps with LANG=3Dfi_FI.utf-8 > - Open example database > - Select "Raportit" -> "Graafiset raportit" -> "Tilastokaaviot..." > - Select options show in attached screenshot > - On the second tab, select all checkboxes > - Click OK This I cannot reproduce. Here is the postscript I get while following your instructions: http://www.gramps-project.org/source/misc_data/alex_stat_chart.ps.gz Does it make sense to you? Did I select wrong options? Do I have some fonts that you don't? BTW, I'm using gramps20 branch of the CVS. Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Eero T. <eer...@ne...> - 2005-09-25 19:48:39
|
Hi, On Sunday 25 September 2005 22:14, Alex Roitman wrote: > > > Is this still an issue? If so, could you please send me the PS file > > > > Here: > > http://www.netsonic.fi/~vellam12/bin/statistics_chart.ps.gz > > It does look broken. > > > > and the recipe of reproducing it? If possible, with the example > > > database. > > > > Note that this problem doesn't exist with English version of the > > report. > > > > Test-case: > > - Start Gramps with LANG=3Dfi_FI.utf-8 > > - Open example database > > - Select "Raportit" -> "Graafiset raportit" -> "Tilastokaaviot..." > > - Select options show in attached screenshot > > - On the second tab, select all checkboxes > > - Click OK > > This I cannot reproduce. Here is the postscript I get while > following your instructions: > http://www.gramps-project.org/source/misc_data/alex_stat_chart.ps.gz Your graph works for me. > Does it make sense to you? Did I select wrong options? Seems OK too. > Do I have some fonts that you don't? Well, at least I was able to view your PS file without problems. > BTW, I'm using gramps20 branch of the CVS. I'm using a CVS version from 14th of this month. Has there been any changes to PS support in between? I can re-produce the problem even by checking just "Age" ("Ik=C3=A4") and selecting descendents of Michael. I'm running SUSE 9.2 and an (old) Garnome version of Gnome. Is any of the Gnome stuff used for the PS generation? - Eero |
From: Alex R. <sh...@gr...> - 2005-09-26 18:53:53
|
On Sun, 2005-09-25 at 23:07 +0300, Eero Tamminen wrote: > I'm running SUSE 9.2 and an (old) Garnome version of Gnome. > Is any of the Gnome stuff used for the PS generation? Not that I could see. This is very strange and does not make sense to me, I have to admit. Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Eero T. <eer...@ne...> - 2005-09-26 18:58:28
|
Hi, On Monday 26 September 2005 21:53, Alex Roitman wrote: > > I'm running SUSE 9.2 and an (old) Garnome version of Gnome. > > Is any of the Gnome stuff used for the PS generation? > > Not that I could see. This is very strange and does not > make sense to me, I have to admit. What stuff required in PS generation is not part of Gramps, just a dependency? We might compare installed version numbers... - Eero |
From: Alex R. <sh...@gr...> - 2005-09-26 19:25:38
|
On Mon, 2005-09-26 at 22:17 +0300, Eero Tamminen wrote: > What stuff required in PS generation is not part of Gramps, just > a dependency? We might compare installed version numbers... This is what PSDrawDoc uses: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D from math import pi, cos, sin from gettext import gettext as _ import PluginMgr import Errors import BaseDoc from Report import run_print_dialog from ReportUtils import pt2cm, rgb_color =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D math and gettext cannot be responsible. ReportUtils only uses points->cm converter and rgb color management. If that was the case then it would fail for you with English text as well. Errors is a pure GUI module with error dialogs. BaseDoc supplies overall doc classes (gnome-independent) and constants. PluginMgr only registers PSDrawDoc generator to enable PS format in reports. I cannot see anything outside PSDrawDoc that can contribute into broken PS under non-ascii locales. Can you update from CVS and see if the problem is there? Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Alex R. <sh...@gr...> - 2005-09-26 20:00:32
|
Eero, On Mon, 2005-09-26 at 11:53 -0700, Alex Roitman wrote: > On Sun, 2005-09-25 at 23:07 +0300, Eero Tamminen wrote: > > I'm running SUSE 9.2 and an (old) Garnome version of Gnome. > > Is any of the Gnome stuff used for the PS generation? >=20 > Not that I could see. This is very strange and does not > make sense to me, I have to admit. Don has figured what the problem is. In your PS, the numbers are using coma as float delimiters, while my PS uses dots. Looks like we either have subtly different locale settings or that you're the victim of a known python bug. We may be able to work around the bug though. What is your python version? What does $ echo $LS_NUMERIC says on your machine? Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Alex R. <sh...@gr...> - 2005-09-26 20:03:42
|
On Mon, 2005-09-26 at 13:00 -0700, Alex Roitman wrote: > What is your python version? What does $ echo $LS_NUMERIC > says on your machine? Sorry, should be: $ echo $LC_NUMERIC or just: $ locale Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Eero T. <eer...@ne...> - 2005-09-26 21:34:07
|
Hi, On Monday 26 September 2005 22:25, Alex Roitman wrote: > On Mon, 2005-09-26 at 22:17 +0300, Eero Tamminen wrote: > > What stuff required in PS generation is not part of Gramps, just > > a dependency? We might compare installed version numbers... > > This is what PSDrawDoc uses: > > ========== > from math import pi, cos, sin > from gettext import gettext as _ > > import PluginMgr > import Errors > import BaseDoc > from Report import run_print_dialog > from ReportUtils import pt2cm, rgb_color > =================== > > math and gettext cannot be responsible. > > ReportUtils only uses points->cm converter and rgb color management. > If that was the case then it would fail for you with English > text as well. I found the problem (I diffed your and my PS files): ----------------- gsave -0.0000 0.0000 0.0000 setrgbcolor +0,0000 0,0000 0,0000 setrgbcolor /Helvetica find-latin-font 14 scalefont setfont ----------------- In Finnish locale the integers and decimals are separated with a comma instead of a full-stop. I hadn't know that LANG sets also LC_NUMERIC etc: gramps> LC_MESSAGES=fi_FI.utf-8 locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES=fi_FI.utf-8 LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= gramps> LANG=fi_FI.utf-8 locale LANG=fi_FI.utf-8 LC_CTYPE="fi_FI.utf-8" LC_NUMERIC="fi_FI.utf-8" LC_TIME="fi_FI.utf-8" LC_COLLATE="fi_FI.utf-8" LC_MONETARY="fi_FI.utf-8" LC_MESSAGES="fi_FI.utf-8" LC_PAPER="fi_FI.utf-8" LC_NAME="fi_FI.utf-8" LC_ADDRESS="fi_FI.utf-8" LC_TELEPHONE="fi_FI.utf-8" LC_MEASUREMENT="fi_FI.utf-8" LC_IDENTIFICATION="fi_FI.utf-8" LC_ALL= According to "man 7 locale": LC_NUMERIC changes the information used by the printf() and scanf() family of functions, when they are advised to use the locale-settings. This information can also be read with the localeconv() function. When outputting numbers to formats (programming languages) which are not locale aware, such as PostScript, locale specific number output functions should not be used, or their locale support should be disabled. I'm not sure whether PostScript programming language is "locale aware", but at least GhostScript interpreter isn't: ----------------------- gramps> LANG=fi_FI.utf-8 gs /home/eero/work/garnome-2.8.0/fifth-toe/gramps/test/statistics_chart.ps ESP Ghostscript 7.07 (2003-07-12) Copyright 2003 artofcode LLC and Easy Software Products, all rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Error: /undefined in 0,0000 Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1057/1417(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)-- Current allocation mode is local Current file position is 612 ESP Ghostscript 7.07.1: Unrecoverable error, exit code 1 ------------------------- > Errors is a pure GUI module with error dialogs. > > BaseDoc supplies overall doc classes (gnome-independent) and constants. > > PluginMgr only registers PSDrawDoc generator to enable PS format > in reports. > > I cannot see anything outside PSDrawDoc that can contribute into > broken PS under non-ascii locales. > > Can you update from CVS and see if the problem is there? This didn't help. - Eero |
From: Alex R. <sh...@gr...> - 2005-09-27 02:00:01
|
Eero, On Tue, 2005-09-27 at 00:53 +0300, Eero Tamminen wrote: > I found the problem (I diffed your and my PS files): > ----------------- > gsave > -0.0000 0.0000 0.0000 setrgbcolor > +0,0000 0,0000 0,0000 setrgbcolor > /Helvetica find-latin-font 14 scalefont setfont Yes, Don did the same thing, so we're on the same page here. > In Finnish locale the integers and decimals are separated with a comma > instead of a full-stop. Yep. > I hadn't know that LANG sets also LC_NUMERIC etc: Depending on the locales version, you may need either LANG or both LANG and LANGUAGE to completely set locale. > According to "man 7 locale": > LC_NUMERIC > changes the information used by the printf() and > scanf() family of functions, when they are advised > to use the locale-settings. This information can > also be read with the localeconv() function. >=20 > When outputting numbers to formats (programming languages) which are not > locale aware, such as PostScript, locale specific number output functions= =20 > should not be used, or their locale support should be disabled. Yes. But Python should take care of that, and it does for me. I have Python 2.3.5 (#2, Aug 30 2005, 15:50:26). What's your version? This used to be a known problem with python, see this page: http://www.python.org/peps/pep-0331.html Quoting from the end: The final patch [11] was integrated into Python CVS by Martin v. L=C3=B6wis on 2004-06-08 I bet that your version does not have that fix. But we may still work around the problem. Don was going to do this tonight. Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Don A. <don...@co...> - 2005-09-27 04:05:01
|
I checked in what I believe to be a fix for this problem. Please test it. Don On Mon, 2005-09-26 at 18:59 -0700, Alex Roitman wrote: > Eero, >=20 > On Tue, 2005-09-27 at 00:53 +0300, Eero Tamminen wrote: > > I found the problem (I diffed your and my PS files): > > ----------------- > > gsave > > -0.0000 0.0000 0.0000 setrgbcolor > > +0,0000 0,0000 0,0000 setrgbcolor > > /Helvetica find-latin-font 14 scalefont setfont >=20 > Yes, Don did the same thing, so we're on the same page here. >=20 > > In Finnish locale the integers and decimals are separated with a comma > > instead of a full-stop. >=20 > Yep. >=20 > > I hadn't know that LANG sets also LC_NUMERIC etc: >=20 > Depending on the locales version, you may need either > LANG or both LANG and LANGUAGE to completely set locale. >=20 > > According to "man 7 locale": > > LC_NUMERIC > > changes the information used by the printf() and > > scanf() family of functions, when they are advised > > to use the locale-settings. This information can > > also be read with the localeconv() function. > >=20 > > When outputting numbers to formats (programming languages) which are no= t > > locale aware, such as PostScript, locale specific number output functio= ns=20 > > should not be used, or their locale support should be disabled. >=20 > Yes. But Python should take care of that, and it does for me. > I have Python 2.3.5 (#2, Aug 30 2005, 15:50:26). What's your version? >=20 > This used to be a known problem with python, see this page: > http://www.python.org/peps/pep-0331.html >=20 > Quoting from the end: > The final patch [11] was integrated into Python CVS by Martin v. > L=C3=B6wis on 2004-06-08 >=20 > I bet that your version does not have that fix. But we may still > work around the problem. Don was going to do this tonight. >=20 > Alex >=20 --=20 Don Allingham <don...@co...> |
From: Eero T. <eer...@ne...> - 2005-09-27 19:26:59
|
Hi, On Tuesday 27 September 2005 04:59, Alex Roitman wrote: > > When outputting numbers to formats (programming languages) which are > > not locale aware, such as PostScript, locale specific number output > > functions should not be used, or their locale support should be > > disabled. > > Yes. But Python should take care of that, and it does for me. > I have Python 2.3.5 (#2, Aug 30 2005, 15:50:26). What's your version? v2.3.3. > This used to be a known problem with python, see this page: > http://www.python.org/peps/pep-0331.html > > Quoting from the end: > The final patch [11] was integrated into Python CVS by Martin v. > L=C3=B6wis on 2004-06-08 > > I bet that your version does not have that fix. But we may still > work around the problem. Don was going to do this tonight. OK. - Eero |
From: Eero T. <eer...@ne...> - 2005-09-28 20:53:59
|
Hi, On Tuesday 27 September 2005 07:04, Don Allingham wrote: > I checked in what I believe to be a fix for this problem. Please test > it. The problem is fixed. Btw. In the meanwhile the colors have disappeared from the StatisticsChar= t legend, do you know why? Also, the latest CVS version of Gramps seems to be lacking filter editor tool, or at least it's not anymore in the tools menu. Where I can find i= t? - Eero > Don > > On Mon, 2005-09-26 at 18:59 -0700, Alex Roitman wrote: > > Eero, > > > > On Tue, 2005-09-27 at 00:53 +0300, Eero Tamminen wrote: > > > I found the problem (I diffed your and my PS files): > > > ----------------- > > > gsave > > > -0.0000 0.0000 0.0000 setrgbcolor > > > +0,0000 0,0000 0,0000 setrgbcolor > > > /Helvetica find-latin-font 14 scalefont setfont > > > > Yes, Don did the same thing, so we're on the same page here. > > > > > In Finnish locale the integers and decimals are separated with a > > > comma instead of a full-stop. > > > > Yep. > > > > > I hadn't know that LANG sets also LC_NUMERIC etc: > > > > Depending on the locales version, you may need either > > LANG or both LANG and LANGUAGE to completely set locale. > > > > > According to "man 7 locale": > > > LC_NUMERIC > > > changes the information used by the printf() and > > > scanf() family of functions, when they are advised > > > to use the locale-settings. This information can > > > also be read with the localeconv() function. > > > > > > When outputting numbers to formats (programming languages) which ar= e > > > not locale aware, such as PostScript, locale specific number output > > > functions should not be used, or their locale support should be > > > disabled. > > > > Yes. But Python should take care of that, and it does for me. > > I have Python 2.3.5 (#2, Aug 30 2005, 15:50:26). What's your version? > > > > This used to be a known problem with python, see this page: > > http://www.python.org/peps/pep-0331.html > > > > Quoting from the end: > > The final patch [11] was integrated into Python CVS by Martin v. > > L=C3=B6wis on 2004-06-08 > > > > I bet that your version does not have that fix. But we may still > > work around the problem. Don was going to do this tonight. > > > > Alex |
From: Alex R. <sh...@gr...> - 2005-09-28 22:41:24
|
On Thu, 2005-09-29 at 00:13 +0300, Eero Tamminen wrote: > Btw. In the meanwhile the colors have disappeared from the StatisticsChar= t > legend, do you know why? No idea, I haven't checked it in a while. > Also, the latest CVS version of Gramps seems to be lacking filter editor > tool, or at least it's not anymore in the tools menu. Where I can find i= t? Only three tools are now in the tools menu. This is because tools are undergoing transition to persistent option handling (similar to the report options). I have yet to convert all the rest of the tools, including filter editor, to the new registration scheme. Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Alex R. <sh...@gr...> - 2005-09-25 17:24:01
|
Eero, Sorry for the belated followup on this. On Thu, 2005-08-18 at 02:07 +0300, Eero Tamminen wrote: > Bug: > There seems to be some problem with Gramps PostScript generation. > I get this error from the GhostScript on the Gramps generated PostScript > file: > ---------- > gs ~/statistics_chart.ps > ESP Ghostscript 7.07 (2003-07-12) > Copyright 2003 artofcode LLC and Easy Software Products, all rights=20 > reserved. > This software comes with NO WARRANTY: see the file COPYING for details. > Error: /undefined in 0,0000 > Operand stack: >=20 > Execution stack: > %interp_exit .runexec2 --nostringval-- --nostringval-- =20 > --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- = =20 > --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 = 3 =20 > %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- =20 > --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- = =20 > --nostringval-- --nostringval-- > Dictionary stack: > --dict:1057/1417(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)-- > Current allocation mode is local > Current file position is 612 > ESP Ghostscript 7.07.1: Unrecoverable error, exit code 1 > ----------- >=20 > When looking at the file with less, it looks quite normal PS i.e. the fil= e=20 > contents are in right format and not (as far as I could see) e.g. > truncated. Is this still an issue? If so, could you please send me the PS file and the recipe of reproducing it? If possible, with the example database. Thanks, Alex --=20 Alexander Roitman http://www.gramps-project.org |