We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

MS Word Document fieldcode checkbox size is different than Aspose Document fieldcode checkbox size for decimals

Aspose.Words Product Family
#1

Tech Support,


I currently have an issue where when I bring my attached MS Word Document into an Aspose.Words.Document object and print it, one of the pages continues onto another page.

Example:
When opening the attachment (transid304.doc) in Microsoft Office Word 2007, the document will contain 8 pages. When printing from Microsoft Office Word 2007, the document will print 8 pages. When importing the attachment into the Aspose.Words.Document object and using the Print function, it will print to 9 pages extending the tables from page 6 into page 7.


Can you please reply with the code needed to collapse page 7 back into page 6 using the Document object, so that we may utilize the Document’s Print function.


Please let me know if you need anymore information reguarding this issue.


Thanks.
- Ryan


This message was posted using Page2Forum (attachment) from Document Class - Aspose.Words for .NET
#2

So from my own research, I have learned a little more about this issue. When printing out the two examples listed above and lining up the two examples pages that have checkboxes and holding them up to a light you can clearly see the checkbox’s are causing the expansion of the page. For some reason, Aspose checkbox’s are about 1 1/2 times larger than MS Word’s checkbox’s.


Here is the field code to create a checkbox in MS Word form MS Word perspective.

{ SYMBOL “168” \f wingdings \s 10.5 * MERGEFORMAT }

Here is the field code to create a checkbox in MS Word from Aspose perspective.

[!FieldStart!] SYMBOL "168 " \f wingdings \s 10.5 * MERGEFORMAT [!FieldEnd!]

It looks like it should be giving the same result, but it’s not. Is there something that I can include as an argument in the checkbox fieldcode that would adjust the box size to make it more similar to MS Word?


Let me know.

Thanks.
- Ryan
#3

Ok, so we believe we have figured it out on this side. The issue is that when using a decimal (10.5) in the field code for wingdings it caused it to default to a value (12) in the Aspose Documents code. Even setting it to 10.0 still made it default to that value (12) in the fieldcode fail. When we modified the field code to 10 without a decimal from 10.5, it accepted the font size.



So question is, is there a way to set the 10.5 font size for wingdings with an additional parameter or will there need to be a fix in the code to handle a decimal datatype in your next patch?


Thanks.
- Ryan
#4

Hi Ryan,

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,

#5

Can I get an ETA on the above fix? When are the latest patches released for your product?

#6

Hi Ryan,

Thanks for your inquiry. Unfortunately, at the moment I cannot provide you any estimate regarding this issue. Our development team will analyze the issue and then we will provide you an estimate

Aspose.Words releases are published at the end of each month and are available for download from here:

http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/category1188.aspx

Best regards,

#7

The issues you have found earlier (filed as WORDSNET-5504) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.