TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
Hi,
already it's possible to export report as TIFF.
But how I can export it specially in TIFF CCITT GROUP3 or GROUP4 for sending over FAX?
It's possibly to your, to extend the exporter options?
Thanks in advice!
already it's possible to export report as TIFF.
But how I can export it specially in TIFF CCITT GROUP3 or GROUP4 for sending over FAX?
It's possibly to your, to extend the exporter options?
Thanks in advice!
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
You suggestion is interesting. We have added your suggestion into our to-do list.
I will let you know when it will be available. Unfortunately, I am not sure that this will be done soon.
I will let you know when it will be available. Unfortunately, I am not sure that this will be done soon.
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
By the way, it would be really very nice, if we can produce FAX reports - it's not really complex at all.
Unfortunately I need this not soon, but yesterday - our "spezial FAX feature" went down on the release planing scheduling
Saving TIFF in CCITT G3/G4 is not the problem at all - there are builtin encoder in .NET 2.0 and above, together with LZW and others. Only what we need are some binarizations - simpy as treshold or comlex as dithering. You can get the code for simpy binarization elswhere on web or I can send it to your. Some free and open source libs offers code for dithering.
The next stuff with images are image manipulation BEVORE encoding: adjusting of contrast, change the DPI, resize and maybe soeme other - in short word the "image improvement" bevore binarizing and encoding, elsewhere we can obtain "unreadable" results.
Actually I've tested the TEXT-Export of Report and it's generally applicable for FAX-Reports.
We need only some really small improvements:
1. Coding the PAGEBREAKS as some control sequence or some parseable (replaceable) explicit sequence in the outrput text file.
2. Resize, preparing and converting the images from report and storing as TIFF G4.
3. Coding the IMAGESEQUENCE as explicit parseable sequence in the output text file. This contain the image name, image information, image link from step 2
4. Evtl. add some FAX control sequences a the top/end of the file like FAX-Number, etc.
5. Evtl. add some OVERLAY control sequences, like report name, watermark, logo, etc.
Generally we get created exactly ONE Text file and SOME TIFF G4 files.
Now there are exactly FOUR possibilities how to process this by EXTERNALLY Fax-Service:
1. Encode Images within IMAGESEQUENCE in some way the original TIFF-image may be restored as file, i.e. BASE64. In this case the FAX-Service parses the text-file, decodes the images and stores as files and replaces the IMAGESEQUENCES by explicit spezifically FAX-SERVER control sequences with image pathes.
2. Same thing as 1, but using of well defined XML-Dataschema. It's nice, BUT really an overhead for FAX-Service.
3. Create an empty subdirectory and put all TEXT and IMAGE files in that subdirectory, the images became simple name and would be directly referenced withing FAX control sequences (like@123 'Image00001.tiff', 100, 100@) within TEXT-File.
4. The same as 3, but all them compressed as single ZIP-File.
Thanks.
Unfortunately I need this not soon, but yesterday - our "spezial FAX feature" went down on the release planing scheduling

Saving TIFF in CCITT G3/G4 is not the problem at all - there are builtin encoder in .NET 2.0 and above, together with LZW and others. Only what we need are some binarizations - simpy as treshold or comlex as dithering. You can get the code for simpy binarization elswhere on web or I can send it to your. Some free and open source libs offers code for dithering.
The next stuff with images are image manipulation BEVORE encoding: adjusting of contrast, change the DPI, resize and maybe soeme other - in short word the "image improvement" bevore binarizing and encoding, elsewhere we can obtain "unreadable" results.
Actually I've tested the TEXT-Export of Report and it's generally applicable for FAX-Reports.
We need only some really small improvements:
1. Coding the PAGEBREAKS as some control sequence or some parseable (replaceable) explicit sequence in the outrput text file.
2. Resize, preparing and converting the images from report and storing as TIFF G4.
3. Coding the IMAGESEQUENCE as explicit parseable sequence in the output text file. This contain the image name, image information, image link from step 2
4. Evtl. add some FAX control sequences a the top/end of the file like FAX-Number, etc.
5. Evtl. add some OVERLAY control sequences, like report name, watermark, logo, etc.
Generally we get created exactly ONE Text file and SOME TIFF G4 files.
Now there are exactly FOUR possibilities how to process this by EXTERNALLY Fax-Service:
1. Encode Images within IMAGESEQUENCE in some way the original TIFF-image may be restored as file, i.e. BASE64. In this case the FAX-Service parses the text-file, decodes the images and stores as files and replaces the IMAGESEQUENCES by explicit spezifically FAX-SERVER control sequences with image pathes.
2. Same thing as 1, but using of well defined XML-Dataschema. It's nice, BUT really an overhead for FAX-Service.
3. Create an empty subdirectory and put all TEXT and IMAGE files in that subdirectory, the images became simple name and would be directly referenced withing FAX control sequences (like@123 'Image00001.tiff', 100, 100@) within TEXT-File.
4. The same as 3, but all them compressed as single ZIP-File.
Thanks.
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
Thank you for such detailed explanation.
Thank you.
Is it possible to provide us with those code free samples. This may make our development faster.You can get the code for simpy binarization elswhere on web or I can send it to your. Some free and open source libs offers code for dithering.
Thank you.
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
Hello Alex,
We have made export with help of native .Net methods. Analysis of this code will require some time. We will let you know in this topic about our progress.
Thank you.
We have made export with help of native .Net methods. Analysis of this code will require some time. We will let you know in this topic about our progress.
Thank you.
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
Hallo Edward,
here some URL's:
http://www.activefax-distribution.com/ftp/af_en.pdf (or _ge.pdf for german)
http://www.activefax-distribution.com/f ... _32_en.exe (or _ge.exe for german)
http://www.activefax-distribution.com/e_produkt.html
http://www.codeproject.com/KB/GDI-plus/ ... eTiff.aspx
http://www.codeproject.com/KB/GDI-plus/ ... erter.aspx
http://www.nextivr.com/ericp/PermaLink, ... b7ede.aspx
http://www.codeproject.com/KB/graphics/bitmapmanip.aspx
http://www.codeproject.com/KB/GDI-plus/ ... g_Lab.aspx
http://www.codeproject.com/KB/graphics/ ... ffect.aspx
* http://www.getpaint.net/index.html
http://blog.bee-eee.com/2008/01/23/c-ad ... -an-image/
http://www.bobpowell.net/image_contrast.htm
http://www.developerfusion.com/article/ ... -contrast/
I can's send more information bevore monday 09.02.09 because of I'm not in office.
Thanks.
here some URL's:
http://www.activefax-distribution.com/ftp/af_en.pdf (or _ge.pdf for german)
http://www.activefax-distribution.com/f ... _32_en.exe (or _ge.exe for german)
http://www.activefax-distribution.com/e_produkt.html
http://www.codeproject.com/KB/GDI-plus/ ... eTiff.aspx
http://www.codeproject.com/KB/GDI-plus/ ... erter.aspx
http://www.nextivr.com/ericp/PermaLink, ... b7ede.aspx
http://www.codeproject.com/KB/graphics/bitmapmanip.aspx
http://www.codeproject.com/KB/GDI-plus/ ... g_Lab.aspx
http://www.codeproject.com/KB/graphics/ ... ffect.aspx
* http://www.getpaint.net/index.html
http://blog.bee-eee.com/2008/01/23/c-ad ... -an-image/
http://www.bobpowell.net/image_contrast.htm
http://www.developerfusion.com/article/ ... -contrast/
I can's send more information bevore monday 09.02.09 because of I'm not in office.
Thanks.
TIFF CCITT GROUP3 / GROUP4 (FAX TIFF)
Hi Alex,
Thank you for your help with it. We have added this feature in our todo list.
Thank you.
Thank you for your help with it. We have added this feature in our todo list.
Thank you.