Which product is apt for me

Hello

Thanks for your inquiry.

  1. Aspose.Words uses standard .NET functions to format values. So you should use the appropriate switches, i.e. switches that properly work with .NET string formatter.
    So, please try using the following switch.
    { MERGEFIELD test # #,##0.00 }
  2. I cannot reproduce the problem with Table of Figure during converting DOC to PDF, it looks exactly the same as in the input document.
  3. Unfortunately, currently there is no way to render comments and revision marks using Aspose.Words. In one of future versions of Aspose.Words we will consider adding an ability to show revisions and comments in the rendered documents (PDF, XPS, SWF, Image). Your request has been linked to the appropriate issue. We will let you know once this feature is available.
  4. Regarding the problem with quality of images, as I can see, the images look like in the input document. (quality is the same). But as a variant, please try specifying JpegQuality to 100. See the following piece of code:
PdfSaveOptions options = new PdfSaveOptions();
options.JpegQuality = 100;

Best regards,

Regarding the size of PDF document.
Size of PDF documents can be reduced only by doing the following:

  1. Decreasing size of images inside PDF (this can be done only be decreasing quality).
  2. Subsetting fonts, which are embedded into the PDF documents. (Aspose.Words does this by default).
  3. Compression of text (Usually decreasing of size is not very big)
  4. Using “Core fonts”. “Core fonts” are 14 fonts, which are supported by PDF viewers by default. We can optionally get rid embedding of these fonts into PDF. But, unfortunately, this feature is not supported by Aspose.Words at the moment. I will let you know once it is available.
    Difference in side of PDF document generated by Aspose.Words and MS Word can be explained by different way of subsetting fonts. For example, if you try to convert a larger document to PDF the size different will be unnoticeable.
    Best regards,

Hi,

When I was searching online, I found in one of your forums somebody reported the same issue, and also an issue is raised in your internal issue tracking system with issue id: CELLSNET-14768. in March,2010.

Can you please let me know if you have any progress on this?. This issue fix is really critical for us to consider Aspose or not.

Thanks,

Hi
Thanks for your request. This number of issue is related to Aspose.Cells product. Please write to the appropriate forum to check the status of this issue:
https://forum.aspose.com/c/cells/9
My colleagues from Aspose.Cells team will answer you shortly.
Best regards,

I understand that this might be Aspose .cells issue. But can’t you do the same fix in Aspose .words.?

Do you think there is no way you can fix this issue? Till now, we were thinking to consider Aspose, may be now, we have to research other products, if you cannot fix this issue.

Hello
Thank you for additional information. Could you please attach your simple input and expected output documents here for testing? I will check them and provide you more information.
Best regards,

Also have you tried doing the same using MS Word? As I can see Aspose.Words output looks the same as MS Word. So I think it is expected behavior, not a bug.
Best regards,

Hi,

I am attaching here the template, data source we used. The expected output which we aer getting from our app where we use MS office object model and Adobe.
Also the output from Aspose. Please let me know what options you can suggest?

Thank you.

Yes, we have tried converting to word, but converting to word is not an option for us. Our final output should be PDF.

Even I tried printing word output from Aspose to Adobe PDF printer, the output is much smaller (82 KB), where as output from Aspose as PDF is huge(324 KB).

So I think this needs to be addressed in Aspose.

Hello
Thanks you for additional information. I have tried converting “Proof+of+Concept+Template_2010.doc” document to PDF using MS Word and the output PDF has size 340KB. The output PDF produced by Aspose.Words is 320KB. As you can see PDF produced by Aspose.Words is smaller than produced by MS Word.
The only thing I can suggest you at the moment, is waiting while we implement supporting of Core fonts, this feature should reduce the size of the output PDF. You will be notified as soon as it is supported.
Also you can try using TextCompression and JpegQuality options. But you should note if you change JpegQuality you can reduce the quality of images in the document. See the following code:

// Open source document.
Document doc = new Document("in.doc");
// Set PdfSaveOptions
PdfSaveOptions pdfOptions = new PdfSaveOptions();
pdfOptions.TextCompression = PdfTextCompression.Flate;
pdfOptions.JpegQuality = 60;
doc.Save("out.pdf", pdfOptions);

Hope this helps.
Best regards,

Hi,

Is there any estimated time frame by when the support for core fonts will be implemented and available?.

Thanks,

Hello
Thanks for your inquiry. Unfortunately, it is difficult to provide you any reliable estimate regarding this feature at the moment. You will be notified as soon as it is supported.
Best regards,

Can you please let me know what is the equivalent method for word Object Model "OrganizerCopy"method in Aspose .words?

Basically I am trying to copy the styles, formatting of a document to another document.

Thanks,

Hello,
Thank you for your request.
Most likely you will find the answer to your question here in this post:
https://forum.aspose.com/t/copy-styles-without-copying-content-like-ms-words-organizer/118731/7

Also please take a look this article in our documentation:
https://docs.aspose.com/words/net/insert-and-append-documents/

Hope this helps.

Hi
Thanks for your request. Maybe in your case you actually do not need to copy styles from one document to another. Maybe it would be better to create an empty document with all required styles defined and use this document as a template for generating your documents. In this case, your output documents will always have a common set of styles.
Even if you need to change styles of an existing document, you can copy all content from these documents into a template with UseDestinationStyles option.
Best regards,

Hi,

Thank you for your reply. I will try that.

Meanwhile, I have one more question. I am trying to create TOC in Aspose.

I found that the following code can be used to create that:

// Use a blank document
Document doc = new Document(); 
// Create a document builder to insert content with into document.
DocumentBuilder builder = new DocumentBuilder(doc); 

// Insert a table of contents at the beginning of the document.
builder.InsertTableOfContents("\o "1-3" \h \z \u");

But the question is that I want to remove page number in the TOC for that I used the same switch which I used in word , but it is not working in Aspose. ’
Can you please let me know what is wrong the in the code below :

builder.InsertTableOfContents("\o “1-3” \h \z \u \n"); this is erroring out.

Thanks,

Hi
Thank you for reporting this problem to us. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is resolved.
Best regards,

Hi,

Thanks for the response. So this will not work for now? There is no alternative for this. HOw long will it take to resolve this?

We are in the process of devleoping Proof of concept and we are facing so many issues. But we decide to use your product in our App and we found some issues like this, then what will happen… will you be able to give us any quick fixes or will we be stuck?

Please let me know.

thanks,

Hello,
Thank you for your request.
Unfortunately, it is very difficult to say how long it will be fixed. First of all developers should analyzed the problem.
We tried to produce a new release every 4-5 weeks. At the end of this week will be released version 10.1. I will try to promote your request and determine the approximate timing of implementation. I’ll let you know as soon as it will be clear.

I found out from developers about the problem. Most likely fix come into the release 10.1 which will be released somewhere at the end of the week.