renemt

Hi there!

Before I do duplicate work, I better ask...

Is there a PDF creator for MAMBO, which considers images when creating a PDF file from a content item?

When I took a look on the pdf.php (in '/includes') and the pdf/Cezpdf-class (in '/classes') I found the Cezpdf-class basically supports image generation in PDF files. As I see the situation, a customization of MAMBO's pdf.php is needed: when there is an <IMG> tag found in the content text string the function 'ezImage' of class Cezpdf has to be called for inserting the image. In this way even other tags like <STRONG> could be properly interpreted...

But the basic question is:
Is there allready an apropriate PDF creator?

Greets,
ReneMT

Sabra

"This Add-On makes it possible to have a PDF version of an article with images and tables:"

http://www.mamboportal.com/index.php...&filecatid=516

:-)


PS: here is the ReadMe file...

<<
PDF with images and tables support

This Add-On turns possible to have a PDF version of an article with images and tables. For this to work I've used other PDF class from FPDF (the same I use in my Support Center Component).

Unfornately not all image formats are supported and some HTML codes aren't used like colors but I consider this as a first step to get it better. I'm working with two more guys on a new HTML class for FPDF.

To install it just uncompress this file and copy/ftp the two folders to your mambo folder. Backup the pdf.php file you already have first.

I haven't done to many tests so if you have problems let me know and I'll try to add a fix to it.
>>

renemt

Well, as expected I get an error when running this script...

Some french part about an unexpected FPDF error and then the meaningfull hint "Some data already have been sent to the browser. Can not send PDF file." (or something like this). I gues it's a problem with PHPs output buffering, isn't it?
So I tried to encapsulate the pdf.php in ob_start() and ob_end_flush() but I did not bring the expected effect... The PDF which was sent (if actually any was sent) was corrupted, so Acrobat could not open it.

Any helpfull hints?

Greets,
ReneMT

__________________
renemt.de - Another great site based on MAMBO.

Sabra

Try this (without laughing at me :-)

open each .php file in a text editor, and simply erase all blank spaces AFTER THE LAST php statement (= ?>)

Sometimes it works...

Oh, and yes, I would be interested to know if it did work for you.

mmx

Mambo uses obstart, so you need to watch out for this if you try to invoke it separately. The place to do it is probably in index.php. For an example of how to do this, you might look at how Alex Kempkins handled this for his sub_template's hacks (posted as a snippet on mosForge).

The FPDF (Free PDF library) does not support image handling, but pdfLIB does. For non-commercial use, the use of pdfLIB is free but it is subject to licensing fees if used commercially.

Emir Sakic (one of the core developers) has a commercial solution for PDF that supports more PDF functions. I have never tried it and have heard no comments from anyone who has.

Interakt released their YAPS PDF library as GNU/GPL under their copyright and it has been implemented on other CMS systems such as Magellan and TYPO3. It does handle png and jpeg images (not gif because of compression licensing restrictions). I believe that it is dependent on Ghostscript for image rendering, but I have heard that it is a good solution.

There are a number of other PDF libraries for PDF out there. I have never tried them.

webamoeba

Do you get somthing like this:

/mambo107/images/stories/nw_Workstation.gif gif : Format d'image non

well I do, I'm assuming this is all to do with "(not gif because of compression licensing restrictions)". hence the

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/mambo107/classes/html2pdf.class.php:406) in /var/www/html/mambo107/includes/fpdf.php on line 998
FPDF error: Some data has already been output to browser, can't send PDF file

is actually irrelevant, that's just to do with the fact that the error messages above have been sent, so no more header info can be sent.