WPF Application , Missing data when converting PDF to Image

[Betsy.jiang]

Dear jperkinsSC,

We had found the solutions for the two issues. But after testing, we found the data missing issue still has an issue, we are fixing it urgently and then provide a hotfix which solves the issues for you.

Sincerely,
Betsy
E-iceblue support team

[jperkinsSC]

Hi Betsy, sorry for the confusion. I understood that, I was hoping for an update on this latest fix.

[Betsy.jiang]

Dear jperkinsSC,

Here is a hotfix which solves your issues basically.
http://www.e-iceblue.com/downloads/Temp ... .9.430.zip
And for the two document(one was sent on 2017/9/26, another was sent on 2017/10/28), they have same name(AMS - GA - Retail Installment Contract_Arbitration.pdf) and the content look like same. After checking, we found they are not the same in fact.
And the data missing issue for the two documents was caused by different reason. Now the data missing issue for two documents and the split issue have been fixed in the hotfix above. There is still a little issue, that is, the position of the data "5376.00" on page 2 changed( only happens on the file sent on 2017/10/28) when converting to image, we are continuing to fix it and will let you know when the hotfix is available.

Sincerely,
Betsy
E-iceblue support team

[jperkinsSC]

Betsy - thank you so much! This hotfix appears to have resolved our issues, with the exception of the amount being offset as you mention. Please let us know when a fix is available for that issue and we should be all taken care of.

Thanks

[Betsy.jiang]

Hi jperkinsSC,

Now we release Spire.PDF Pack(Hot Fix) Version:3.9.431 which improves the offset issue, please check the screenshot. There are some difficulties in achieving the same result at present. We will continue to investigate the issue and let you know if there is any good news.

Sincerely,
Betsy
E-iceblue support team

[jperkinsSC]

Besty

Thanks for the fix, All the known issues in this build are solved, but we are facing a new issues in the latest build of spire.

1. When we start render pages of pdf into images it takes too much time at document.SaveAsImage() method for each page as compare to previous version of spire.pdf.wpf(v3.8.112.6240). which results in increase the total time of rendering a complete pdf document. we have tested current version of spire with 6 page document it takes approx. 4 min to render images which is too long because in our project we need to render 10 to 15 document of about 25 to 30 pages that results in 10 to 15 min in rendering only. We have also tested spire v3.8.112 to render same document and it takes 20-25 seconds for all 6 pages.

2. Secondly when we create image of the pdf, the text font size become much bolder and blur. send the image file via email, you can notice the date and other fields being bold and blurred.

We have send the document via email ,which we are testing.

Here is the code and document we are using.

Code: Select all

private void button_Copy_Click(object sender, RoutedEventArgs e)
{
     using (PdfDocument document = new PdfDocument())
            {
                document.LoadFromFile(path1);
                for (int i = 0; i <= document.Pages.Count; i++)
                {
                    var img = document.SaveAsImage(i, 192D, 192D); //this point is taking too much time
                    SaveImage(img, path1.Remove(path1.Length - 4) + "_Page_" + (i) + "_grf.Jpg");
                }
            }
}

private void SaveImage(BitmapSource image, string targetPath)
        {


            var encoder = new PngBitmapEncoder();
            encoder.Frames.Add(BitmapFrame.Create(image));
            using (var filestream = new FileStream(targetPath, FileMode.Create))
            {
                try
                {
                    encoder.Save(filestream);
                }
                catch (Exception e)
                {

                }
            }
        }



Regards,

[Jane.Bai]

Hello Mubasher,

Thanks for your letter.
When trying the old version 3.8.121, I got an exception so I did not get the time cost. Anyway, I have reproduced the issue with the latest hotfix and referred it to our dev team for an optimization.
In regard to the second issue, sorry I didn’t encounter it. Please make sure you were using the latest hotfix(Spire.PDF Pack(Hot Fix) Version:3.9.431). You can see the attched result image in the email that I sent to you.
If the second issue still troubles you, come back and share more details on the environment that your project is running on .
Looking forward to your reply.

Sincerely,
Jane
E-iceblue support team

[jperkinsSC]

Hi Jane - I will let Mubasher respond to your technical questions, however I wanted to see what the ETA is on getting the time to load optimized? We very much need to get this finalized as soon as possible. Thank you
-Brent

[Jane.Bai]

Hi Brent,

Sorry for the late reply.
After our dev team's deep and thorough investigation, we found the optimization might not be implemented at present due to the particularity of the pdf file. Since all the text in the sample document are drawn by dots and lines, which is extremely time-consuming, the total time increases in the end. We will consider a further investigation on this account in the future. Once there's any progress, I will let you know.
We apologize for the inconvenience caused.

Sincerely,
Jane
E-iceblue support team

[jperkinsSC]

Jane

That is quite strange to know, as we mentioned earlier that the time taken in the previous build (3.8.121 to be exact) was absolutely fine , it used to take about 30 sec but in the new build it taking more than 4 minutes on the same document,

There is one other option, We have also asked our client to fix the documents at there end (for which we initially started this post), if you are unable to resolve the time problem we are hopeful they might correct it at there end, in that case we will use 3.8.121 version of spire,

but there we have issue with the file size when splitting the documents , We have uploaded the sample documents at

https://secureclose.azurewebsites.net/spire.rar

containing all the documents we splitted using " document.Split" function,


the New version splitted 8mb / 6 page document into separate 6 pages totalling 7.59 MB
the old version splitted 8mb / 6 page document into separate 6 pages totalling 35.9 MB

If you just fix that on version 3.8.121 so we will use this build instead of the latest one,

Regards

[Jane.Bai]

Hello Brent,

One strange thing, when I use v3.8.121 to save pdf pages to images, I always got the"Index out of range" exception. I wonder how you manage to do it. Could you share your running environment and the Region and Language in your system like Server 2012R2, 64 bit with English(US)?
Amyway, I have noticed the spliting issue and referred it to our dev team for a further investigation. If everything went well, we would consider your suggestion on fixing the splitting issue on the basis of version3.8.121. Once there's any good news, I will let you know.

Sincerely,
Jane
E-iceblue support team

[jperkinsSC]

Jane

you have to use ""doc.SaveAsImage(0, 192D, 192D)"" in new build and ""doc.SaveAsImage(1, 192D, 192D)"" in the old build ,

in the old build the page index starts from 1 while in the new one it is corrected to 0

Looking forward for your response

Regards

[Jane.Bai]

Hello Brent,

Thanks a lot, I managed to reproduce it in the end. Yes, we have made the change of page index in the new wpf version.
Also, there's a good news for you. Through many obstacles, our dev team finally found an approach to the optimation issue, so that we decide to implement the fix on the latest version rather than v3.8.121. Once the hotfix is available, I will let you know.

Sincerely,
Jane
E-iceblue support team

[jperkinsSC]

Hi Jane- hope you had a good weekend! I’m glad to hear you guys have solved the issue! Do you have an update on when we can expect the hotfix? We are anxious to be able to deploy. Thanks

[Jane.Bai]

Hi Brent,

Sorry there's no exact date when the hotfix will be released. Now your issue has been resolved and it is in the testing phase. we wil try our best to push it forward and provide the hotfix. I'll let you know when it is available.

Sincerely,
Jane
E-iceblue support team