Choosing report tools

[Graeme]

1/wow cool .. does your pdf implementations includes correct non latin fonts handling (font subsampling),

fpPDF (already included in FPC Trunk) does handle Unicode text. For unicode text to display correct, you need to embedded a font that includes the glyphs you used. At the moment fpPDF will embed the whole font into the PDF, thus the PDF's can get a bit big if you use lots of different fonts in the same document - font-subset embedding (partial font embedding) will be implemented soon.

[Graeme]

The reason I chose AggPas (instead of say FPCanvas) is because AggPas has far superior anti-aliased and sub-pixel graphics rendering. (see here) Saying that, a FPCanvas/FPImage version will probably be implemented too.

As it wasn't much work, a FPCanvas/FPImage report export filter was implemented for fpReport as well. As expected the image rendered output is not as good quality as the AggPas version (eg: no anti-aliased line drawing). But at least now we have a choice of two report rendering filters that can generate PNG images. 

[Ondrej Pokorny]

font-subset embedding (partial font embedding) will be implemented soon.

This is very good news!

[talorigomat]

Is there any more news on fpreport?   Eager to give it a try

[Graeme]

The first release is very close now. I'm making some final changes which will stabilise the reporting API. After that Michael van Canneyt wants to make the initial release. This should happen in the next 2-3 weeks I guess - if not sooner.

[marcinh]

Any hope to release or project is dead ?

[Graeme]

@marcinh:
fpReport has been implemented and is being used internally here. I was only tasked in implementing it. Michael is in charge of making it public.

[Mocte]

@marcinh:
fpReport has been implemented and is being used internally here. I was only tasked in implementing it. Michael is in charge of making it public.

I'm eager to put my hands on this tool