Re: [web2py] FPDF issue

2013-10-29 Thread step
The latest fpdf code commit is dated August 15. I checked its source code against the one bundled with web2py 2.6.4-stable and they appear to be identical. On Tuesday, October 29, 2013 8:06:23 PM UTC+1, Massimo Di Pierro wrote: > > Should I do that too? > > On Tuesday, 29 October 2013 13:30:58 U

Re: [web2py] FPDF issue

2013-10-29 Thread Massimo Di Pierro
Should I do that too? On Tuesday, 29 October 2013 13:30:58 UTC-5, Mariano Reingart wrote: > > You can try to download the fpdf source code from the repository (see > the download zip link) and update your web2py distribution: > > http://code.google.com/p/pyfpdf/source/browse/ > > Please let fol

Re: [web2py] FPDF issue

2013-10-29 Thread Mariano Reingart
You can try to download the fpdf source code from the repository (see the download zip link) and update your web2py distribution: http://code.google.com/p/pyfpdf/source/browse/ Please let follow this on the fpdf site: http://code.google.com/p/pyfpdf/issues/detail?id=66 Thanks for reporting it!

Re: [web2py] FPDF issue

2013-10-29 Thread step
Fair enough, Richard, I'm providing sample code here, and I will link to it in the issue report. Comments in the sample code explain the 0x95 codec error and also ask some questions. Thanks for your help. Download TTF font DejaVuSans.ttf and copy it into gluon/contrib/fpdf/ You can download it f

Re: [web2py] FPDF issue

2013-10-28 Thread Richard Vézina
did you user your_string.decode('utf8') before passing to FPDF?? I think you have mistake in your code, you should provide example code in you issue report!! Richard On Mon, Oct 28, 2013 at 2:40 PM, step wrote: > I discovered and reported in > http://code.google.com/p/pyfpdf/issues/detail?id=

[web2py] FPDF issue

2013-10-28 Thread step
I discovered and reported in http://code.google.com/p/pyfpdf/issues/detail?id=66 an issue with gluon/contrib/FPFD. Basically, rendering HTML tags as PDF may trigger a utf8 codec error because fpdf/html.py sets the bullet character as '\x95'. As a work-around I have replaced '\x95' with '*'. -