pdf- Export

rbuser

Hello, I do run the function PsRBExportDevices and go get pdf files in a
uge size about 390kByte.

The properts cmMaxCompress seems not to work.

If i print the same document with (Win2PDF) the filesize is about 8 kByte.

My Code:

PsRBExportPDF1.CompressionMethod:=cmMaxCompress;

ppReportSB.DeviceType:='Adobe Acrobat Document';

ppReportSB.Print;

did you know a better tool?

nicocizik

Hi Peter,

You may try contacting Pragnaan to see if there was a bug fix if the
compression does in fact not work correctly. There are two other third
party export components that use similar compression techniques available.

TExtraDevices: http://www.waler.com

eDocEngine: http://www.gnostice.com

--

rbuser

Peter Schuster wrote:

If youuse EMBEDFONT as an option then every PDF has at little 300kB for
placing used font.

What is better is to embed subset ... or even better do not embed any
font - if You use English and standard Windows fonts!!!!

;-)

rbuser

Hi Peter,

There are various aspects that affect the size of a PDF file. Let me explain as
many as I can:

1. The compression of the page stream, which contains the actual text and
graphics on a page that you see in Acrobat Reader. This feature, the one you are
talking about below, is supported by most of the exporting products on the
market today.

2. Do you use RichText components in your report? It is really going to affect
the size of your PDF file, depending on the way the exporting tool converts
RichText. Most of the other exporting tools convert RichText to an image
(BMP/JPEG) and put that image into your PDF. RichText can actually be converted
to rich editable text, which makes it more useful for searching, for
high-quality view/print and of course keeping your PDF file size way smaller
(1/20 and more). RichText conversion to rich editable text is of course a lot,
lot more work than converting it to an image.

3. Do you have any metafile images (EMF/WMF) in your report? Metafile images too
are converted to (BMP/JPEG) in most of the other exporting tools, resulting in a
PDF that is much heavier and of lower graphic quality. In fact metafiles can be
converted to PDF drawing commands (lines, arcs, shapes and so on), which give
you again a sharp print quality PDF file that is very light.

4. Font embedding/sub-setting/selective embedding. Font embedding too can be
further optimized to include information for only those characters your report
uses. How properly this is done matters to the PDF file size. Furthermore, it
can be made possible to embed/sub-set embed only certain fonts used. For
example, if you use Arial and a custom font of your own, you could choose only
to sub-set embed the custom font and not the Arial font (which will likely exist
on most systems). eDocEngine VCL provides a way to exclude the fonts that you
don't want to get embedded.

5. Using Chinese and other Unicode text in your reports. Here again some of the
exporting tools use font embedding, which increases the PDF file size
tremendously. There are other ways of supporting Chinese, other multi-byte and
non western character sets, with the use of Unicode encodings. This again
greatly reduces the PDF file size.

6. Formatting of the page stream and other elements in the PDF file. How the PDF
file is actually written (the internal formatting) does matter too. For example,
a PDF document of about 100 pages can easily contain over 10,000 lines of PDF
code (the PDF file when you open it in a text editor). Now saving 2 bytes per
line results in a saving of 20K!

All of the above aspects have been well taken care of in eDocEngine but you
don't have to take my word. Please have a go with the free trial versions
available at:
http://www.gnostice.com/edocdownload.asp

There are also several EXE demos into which you can load your saved report file
and export to PDF and several other formats.

Some more info...

Why eDocEngine is the preferred solution for exporting reports?
===============================================================
* Supports exporting to over 20 popular formats, including PDF, RTF, HTML,
Excel, TIFF, SVG, PNG, JPEG, Metafile and many more.

* Integrates tightly with your reporting tool to enable CODE-FREE
configuration and execution at design-time as well as run-time.

* Allows for extensive configuration of exports through vast set of
intuitively named and grouped properties.

* Charts and Metafiles are rendered as vector graphics to ensure sharp,
scalable graphics in the generated PDF, RTF and other supported formats.
Vector graphics also ensures files are extremely compact and easy to
distribute.

* Supports RichText rendering as RichText (not image) in all document
formats ensuring crisp documents that can be text searched and enlarged
without loss of quality.

* PDF engine supports full set of advanced features including, compression,
encryption, TrueType fonts, font embedding, font sub-setting,
international characters (European, Chinese, Japanese...), bookmarks,
notes annotations and more.

* All standard and custom controls are exported, WITHOUT the need for
extra coding on your part.

* Excel and all spreadsheet engines support intelligent cell formatting
enabling values to be encoded in the correct format, automatically.

* Supports End-User configuration of exports through *customizable*
run-time dialogs.

* All engines of eDocEngine are highly optimized for HIGH-SPEED export
of reports.

* Highly flexible architecture enables custom programmatic exporting. For
example, you can combine multiple reports then insert your own custom
page (using the eDocEngine API), then append a few more reports and
make a single output document of them.

* And much, much more...

Let us know if you need further assistance.

--
Girish Patil
Gnostice Information Technologies www.gnostice.com
---------------------------------------------------------------------
Gnostice eDocEngine (http://www.gnostice.com/edoc_engine.asp) -
Electronic document creation, PDF eForms and report export components

Gnostice PDFtoolkit (http://www.gnostice.com/pdftoolkit.asp) -
PDF document management and PDF eForms processing components
---------------------------------------------------------------------