Font problem in pdf roster when using XAMPP

[GoogleCodeExporter]

I'm not the one getting the errors and I'm not getting much feedback on my
suggestions for solution.

What steps will reproduce the problem?
1. Have XAMPP installed.
2. Pressing the pdf roster link gives error.

What is the expected output? What do you see instead?
PDF roster doc is expected, instead you see an error:
Warning: FPDF::include(tahoma.php) [function.FPDF-include]:
failed to open stream: No such file or directory in
C:\xampp\php\PEAR\fpdf.php on line 476

What version of the product are you using?
0.37

Please provide any additional information below.

I suspect the include statement that PEAR needs is the bad guy in this.
Does anyone have XAMPP (PEAR?) and OBBLM installed without problems with
pdf roster? (With the include entry for PEAR in php.ini?)

A workaround is to define FPDF_FONTPATH and point to where the fonts are
(tahoma in this case).

/Daniel

Original issue reported on code.google.com by blodae@gmail.com on 11 Feb 2009 at 9:03

[GoogleCodeExporter]

Well, "failed to open stream: No such file or directory in ..."
almost always means that the path specified is incorrect or the file trying to 
be
opened has file permissions which does not allow the webserver to open the file 
-
it's quite likely it's the latter.

Original comment by Nimda...@gmail.com on 11 Feb 2009 at 12:34

[GoogleCodeExporter]

My very shallow experience of PEAR makes me lean towards the former. I 
suggested a
line in pdf_roster.php:
define('FPDF_FONTPATH','font/');
which was suggested in fpdf.org forums for similar problems. "font/" is in 
regard to
where fpdf.php resides and can be set to an absolute path. Perhaps it should be
"pdf/font/" since handler.php is the one starting pdf roster?

As I see it, what the error says is that it cant find the font files. Either 
they
cant be read because of wrong permissions, or it's looking in the wrong dir.

Original comment by blodae@gmail.com on 11 Feb 2009 at 1:01

[GoogleCodeExporter]

Well it is satisfying enough for me if the correction you describe works on 
both your
system and his?

Original comment by Nimda...@gmail.com on 11 Feb 2009 at 5:16

[GoogleCodeExporter]

When I get some feedback from Masia I'll update.

Original comment by blodae@gmail.com on 11 Feb 2009 at 7:39

[GoogleCodeExporter]

I'm begging to kind of give up on this one...
I mean, this is the only case of the error we have, and therefore I find it very
probable that it is due to a bad web server settings on his side?

I propose we close this one for now, until we get more feedback on this issue.

Original comment by Nimda...@gmail.com on 9 Mar 2009 at 11:47

• Changed state: Invalid

[GoogleCodeExporter]

No new info from Masia. I guess we can reopen if this becomes an issue again.

/Daniel

Original comment by blodae@gmail.com on 9 Mar 2009 at 1:03