Hi.

I have found another issues when doing flatten all fields. One related issue is also found in this topic link
I am not going to cover it then.

The fields are calculated and also are formated as numeric or as percent. The flatten all fields is applied.

1. The percent is not shown, instead just a decimal number. For example:
    a) 80%

After flatten all fields, I get:
    a) 0.8

2. The calculated numeric field somehow looses one decimal point. For example I had 2 fields with original values:
    a) 0,80
    b) 0,11

After flatten all fields I get instead:
    a) 0.8
    b) 0.0

I have included sample files and descriptions.

Hi,

Thank you for considering Aspose.

As you mentioned the problem is same like

http://www.aspose.com/Community/Forums/thread/99324.aspx

I am not sure that Aspose.Pdf.Kit supports it. So can you please send us your code with pdf files, I will discuss this with the developer and will let you know as soon as solution is found.

Thanks.

Dear DMINATOR,

This bug was reproduced. It was reported as [PDFKITNET-3935] and is expected to be fixed within two weeks.

Best regards.

---

Luke Fu
Product Developer
Aspose Changsha Team
About Us
Contact Us

Please try the attachment before we publishing the hotfix.

Form.FillField() has been promoted for format supporting. Text Field with Percent/Number/Time/Date format can be filled correctly. Note: this feature is especially for AcroForm fields, other than XfaFrom ones.

---

Tommy Wang
Lead Developer
Aspose Changsha Team
About Us
Contact Us

Hi.

I tried but haven't noticed any difference with percentage fields formating. It is saved the same way as it was before: 0.115 should be 11,5%

The other thing I am little concerned about is the truncation of the calculated field:

The field formatting parameter specifies that it should have 2 numbers after separator. The flatten produces only one, and it also truncates the result making the calculation result incorrect.
In the original pdf example:

There is Total = 5,00
Tunnustada = 4,20
Praakida = 0,80

As you can see if you sum it up you get that 5,00.

Now with new dll it works this way:
Total = 5,00
Tunnustada = 4.2
Praakida = 0.7
Which gives 4.9 if sum it up.

However I checked the fdf and noticed that these fields get these values the first time:
(pdfTFPraakida)/V(0.7)
(pdfTFTunnustada)/V(4.2)
So I am not sure if this is actually aspose problem.

Dear DMINATOR,

That is very strange. Did you test with the template in the attachment Format_Bug.zip ? I tested the example with the uploaded dll, 0.115 is displayed as11,5% correctly, as you can see in the attachment. Please make sure that you replace the old dll indeed.

Besides, I did found something wrong with field "Praakida". It is defined in "custom calculation script" such as JavaScript, discribed as:

//Calculates how much of the field is flawed and how much is accepted

var total = this.getField("pdfTFKasvupind").value;

var tun_var = this.getField("pdfTFPraakida").value;

var prk_var = this.getField("pdfTFTunnustada");

prk_var.value = (total - tun_var);

But unfortunately, this feature is not provided in our product. Thus please avoid defining a field value in "custom calculation script". Instead, only five basic calculation operations are supported, including: sum(+), product(*), average, min and max.

Sorry for the inconvenience & Best regards.

---

Luke Fu
Product Developer
Aspose Changsha Team
About Us
Contact Us

Hi.
Yes I am sure I tried the latest dll, I have one test application I use for that, and I tried all the documents that I had previous issues with (maybe this is nothing but with the included dll I didn't find the Aspose.Pdf.kit.xml).

 I think I can give you the whole project with templates and source so you can check it. ( I couldn't include the whole project files (the aspose dlls) it made the archive too large > 2,5 MB So i had to remove the dll, you need to add this aspose dll to the project in order to build it )

About the calculation issue, I think you are right and this is not the aspose issue so I am not going to ask anything from you. The problem with the pdf calculation is the rounding. I am going to try to resolve that by applying rounding within the calculation script itself.

Hi,

Thanks for your sharing resource and I was able to reproduce the problem. This is really strange, hehe.... Anyway, I am going to find out the reason, expected within one week.

Best regards.

---

Luke Fu
Product Developer
Aspose Changsha Team
About Us
Contact Us