Received : 2007/06/22 10:13:44
Message : First your product is AWESOME! Second we are having a problem in that we run a merge with images in it and we are having to break the files into either 100 or 200 pages due to the output file having a glitch. When you page through and hit a certain page it will jump to the end of the file or beginning (whichever way you are paging up or down).

We can run letters with 1,000+ pages, but this one file which has a large image with images on top of the large image on every page is a problem.

Also when we try to PDF this using your PDF tool, we are not getting the result we expect. We can PDF it from Word and it works. However your tool changes fonts in the document and splits the background image onto a second page so we have one page becoming two which does not work too well.

Any help we would appeciate.

Thank you

---

This message was posted using Aspose.Live 2 Forum

---

Viktor Sazhaev
Software Engineer, Aspose Auckland Team

Please note, that generating extremely large documents is not a recomended practice. You see, if you have problem with 1000+ pages document it is extremely hard to say whether this glitch is of Aspose.Words or MS Word itself and also it will be practically impossible to reproduce and trying to fix the error.

Best regards,

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team

We are only trying to generate a 135 page document and word can do this without any problem and it works if I break it into 100 page files for merging with your software.

Ok, please attach the problem document. I will try to research the issue.

---

Vladimir Averkin
Developer/Technical Support
Aspose Auckland Team

Hi Rollie!

 

I investigated the problem with rendering your document to PDF. There were issues even if I took only the first page. They are related to Aspose.Pdf. I addressed this to Aspose.Pdf team. They created a new defect in the defect database under number PDFNET-3276 and will work on it.

 

Also I saw a glitch on page 113. The best thing I can recommend is to split these certificates by 100 or even 50 items. Most probably smaller documents would not bring such effects.

 

Regards,

---

Viktor Sazhaev
Software Engineer, Aspose Auckland Team

Thanks for the response.

I'm glad the PDF team is working on the problem.

However splitting the file is not an answer I was looking for, for this is not possible and I would expect that if word can generate a valid document your software should be able to also.

If we process 1,000 pages we are supposed to send 50 files to our print facility and ask them to print these one by one by one? Sounds a little silly does'nt it? Also Am I supposed to monitor ALL of our documents that are going to be generated using your tool to make sure that this glitch does not appear in any other documents? Or maybe break apart all our 1,000's of pages of documents into 50 pages each????

I would hope that this 'glitch' is being researched and will be resolved soon.

Thank You

Hi Rollie.

 

As I see your complain of the two problems:

    1. ‘Glitch’ on page 113.

    2. Rendering in PDF format.

 

About the ‘glitch’. You tried to create such a document with MS Word and it was good. So you had used MS Word Automation before you tried Aspose.Words, hadn’t you? Please send us that document which doesn’t have the ‘glitch’. The next thing is the template. Most probably you have some document with only one page to multiply it programmatically and insert different names from some other source. Please send us that template as well. It may be (and most probably is) a rendering/scrolling issue in MS Word itself. But to tell you exactly we have to compare with Automation result. Internally your document is consistent, no problem with it’s structure.

 

About the rendering to PDF. This is a defect of another product - Aspose.Pdf. The team is working on that. But I cannot promise anything of behalf of them.

 

 

P.S. To send large documents it’s better to archive them with WinRAR archiver if you have it. You can also use the technique with volume splitting as the last time.

 

Regards,

---

Viktor Sazhaev
Software Engineer, Aspose Auckland Team

We can generate sometimes 200 pages and sometimes 100 pages without a problem and have to look at the document to determine if it was generated correctly. We are trying to have an automated process that runs and generates documents that then get printed and processes 1,000+ pages per run without having to look at the document and page through every week.

We no longer have the document in a MS Word capable merge environment or have the time to convert it back. We have since converted this to an Aspose Engine that we wrote that generates and runs this application once a week.

My comment is that we generate many other documents using Apose that are 1000+ pages long with no problems its just that this one has a problem and must be some sort of glitch in the Aspose program.

So what would the MS Word generated document get you? That process worked with no problems.

And I understand the the PDF  process if being looked at.

Your product is terrific in every way I just need this one little glitch cleaned up and if I am doing something in the document that needs to be changed please let me know.

Thank you for all your effort and help so far

Rollie

Rollie,

 

We are strongly aimed to help you. But we still don’t have enough information.

 

I experimented with your document in many cases. For instance I saved it in different formats, removed first 111 or 112 pages etc. I figured out that removing previous (good) pages don’t eliminate the ‘glitch’. If I save it as RTF or WordML nothing more strange happens. But all that is not enough to say what do we face.

 

Even if I was certain that it is a MS Word bug you would tell me that Aspose.Words goes wrong. I can repeat that your document is structurally correct. So we cannot find any glitch inside its model. All it needs to look correctly in MS Word is a bug free version of MS Word.

 

So we have to reproduce the process which gives a document with glitch. I figured out from your post that you don’t have any template and generate the document from scratch. Is it true? How many times per week it doesn’t matter. Please provide us the information how you do that. For instance you have several images, a database with names of people who get certificates and a C# program utilizing Aspose.Words. The program creates an empty document, takes names from the database in a loop and puts a page for every name to the document. Pages are constructed using frames, drawing objects and images. Of course some overall initialization and finalization is needed. Send us that program. At least the fragment which deals with Aspose.Words. Provide us with technical information, not emotions.

 

We have already got a workaround. You can save the document in WordML rather than in DOC format. Don’t use RTF here because of it’s tremendous size under assumption you put 1000+ page in one file. WordML opens and scrolls in MS Word without any ‘glitches’. If you want to get a PDF document from that we need to wait for the fix in Aspose.Pdf. Of course I’ll tell you when it is ready.

 

 

Thank you for understanding,

---

Viktor Sazhaev
Software Engineer, Aspose Auckland Team

Thanks I havent tried the ML saving but I do have now more information which may help.

We generate numerous documents of diiferent criteria then Append them together using the appending code that you have on your site somewhere the problem seems to manifest itself when we merge a certain type of document in I can send you the different documents and the code I use to append them together if that would help.

Doc 1 2 pages            Appends Fine

Doc 2 111 pages        Appends Fine

Doc 3 12 Pages         Creates Glitch at page 113

Thanks for the speedy response.

Hi Rollie.

 

That's very interesting. I see that the glitch appears somewhere at the point where 2nd document finishes and 3rd one starts. And the source documents of course don't have any glitches.

 

Would you send me these three documents and the code you are using to merge them? I hope it could reveal the cause of such a strange behavior.

 

I experimented with conversion to PDF on the Aspose.Pdf version they plan to publish early next week. There is no any glitch after conversion. Don’t worry about it. Nevertheless I saw some issues in the result and already wrote about them to Aspose.Pdf team.

 

First thing is that the image put on the background (the one with "Washout" style) doesn't fit the page and they scale it. Note that on the original pages of your document last line of text is not visible. Consider scaling it in the source to make everything fit well. To imitate washout style in PDF you can change the original colors to make the image look faded.

 

Second, there are several boxes with white background fill on every page. In PDF they become non-transparent. I removed fill color and the white boxes disappeared.

 

Third, there are images which are rendered on the white background. Aspose.Pdf team recommend experimenting with their opacity.

 

In general, it is difficult to get the result PDF look equivalent or even similar to the source DOC. This comes from the principal differences in these formats. So we have to make assumptions and approximations. It is mainly true for documents with complex layouts. If you need exactly PDF (not DOC or WordML) then only experiments with sources could give suitable result.

 

Best regards,

---

Viktor Sazhaev
Software Engineer, Aspose Auckland Team