Lol, I'd say this is a bit off topic :)
I tend to use PDF libraries as late in the game as possible.
Basically, I do this:
1. Don't bother learning to use a PDF library, and spending hours
farting about trying to design a reports using a code API.
2. Create reports as web pages in HTML /
ASP.NET, just like any other
pages in your site. You can work with the design and layout tools you
know and love - such as CSS and notepad :). HTML gives you great
control over character sets, directional layout for RTL languages,
images, CSS etc. You also can use cool
ASP.NET graphing libraries,
image libraries, etc etc.
3. Find a PDF library that can **import** a web page to the standard
you need. Usually something like this:
SomePDF.AddPage("
http://127.0.0.0/Invoices/PrintPreview/1234",
Options.AddPageNumbers);
4. So, you can now turn web pages into PDFs. You can stream them to
the browser like this: Response.WriteFile( SomePDF.OutputStream );
I've used this approach on 5 projects so far (NET and Ruby on Rails),
and I personally like it a lot. The 2 libraries I've really enjoyed
are these:
- AbcPDF (.NET) -
http://www.websupergoo.com/abcpdf-1.htm. Try the
online demo, it's amazing. They used to give out free licenses if you
put them on your home page.
- Pd4ML (Java, .Net in public Beta) -
http://pd4ml.com/. The
international (Arabic, Central European etc) support in this was
perfect, and it's fast.
Tobin
On Sep 15, 4:56 pm, "Will Shaver" <
will.sha...@gmail.com> wrote:
> Thanks all for the responses.
>
> -Will
>
> On Mon, Sep 15, 2008 at 7:18 AM, Tim Scott <
timasc...@gmail.com> wrote:
>
> > I have quite happily used NFOP.
http://sourceforge.net/projects/nfop