Hi Muhammad, what is the status on the performance degradation issues of splitDocument?
When this is fixed, we will test whether the textareas are included in the wordcount.
Hi Richard,
Performance issue will be resolved gradually and it can take some time. At the moment we are not in a position to share any ETA. We will let you know as soon as some progress on this issue has been made.
Sorry for the inconvenience.
Best Regards,
Hi Muhammad, do you’ve already got an idea what does cause the performance issues?
Hi Richard,
SAASWORDS-206 has been resolved but SAASWORDS-207 which was related to performance has not been resolved yet. No matter you split one page or all pages, Aspose.Words builds the document layout for the whole document in memory so it takes same amount of time.
The problem is not because of document size or number of pages; it is because the document is in simple text format and simple text documents currently take more time. With the increase in number of simple text pages, time to split documents will also increase.
The issue has been included in our near future plans but we are not in a position to share a concrete ETA for this issue.
Sorry for the inconvenience.
Best Regards,
Hi Muhammad, can you share more info on the performance related issues discussed in this topic? We are waiting on this feature to be released, so we can upgrade to a more expensive subscription plan.
This feature will enable us to save a lot of expensive support time, so please let me know the ETA for the performance improvements.
Hi Richard,
The time taken in splitting is directly proportional to the number of text pages in the document. The more number of text pages, the more time it will take. Same is the case with MS Word; it also takes more time for such documents.
Performance has been improved a bit but you will not see significant reduction in split time anywhere in near future. The issue has been closed as it will not be available in near future.
We are sorry for the inconvenience.
Best Regards,
Hi muhammad,
Today we’ve started testing the “Words statistic” call again. We started by testing a document with a textarea, but they are not added to the wordcount. Can you also add the textareas to the wordcount? Last march you said this was fixed, so maybe this still is buggy?
Next to that we also need a separate count per page with the number of words the footnotes are per page: Get statistics on a document|Documentation
So, the “PageStatData.Page” ideally and if semantically correct has the following data:
- Page number
- Word count (which includes words in textareas)
- Paragraph count
- Footnotes wordcount (which by default are not included in the total wordcount)
Concerning the “splitDocument” action, the documentation also doesn’t seem to be up-to-date:
Hi Richard,
We are investigating it and will update you shortly.
Best Regards,
Hi Muhammad, can you confirm that:
1. Textareas are not included in the wordcount at the moment
2. Footnotes will be added to the “PageStatData.Page” array separately
This actually is the most important issue for us at the moment.
Hi Richard,
I am able to include or exclude text areas and footnotes at my end. Can you please share what issue do you see at your end and share a document to reproduce the issue?
All you need to do is to set a parameter (includeTextInShapes) for text areas and a parameter (includeFootnotes) for footnotes to include or exclude text areas and footnotes respectively e.g.
http://api.aspose.com/v1.1/words/Testdocumentwoordentellen.docx/statistics?includeTextInShapes=true&includeFootnotes=true
Best Regards,
Great news! So you mean that it did work, but the parameters aren’t enabled by default and weren’t documented properly yet? We will update you once we tested these parameters.
Thanks for being patient. We have good news for you i.e. SAASWORDS-206 has now been resolved. You may now please re-test your scenario with Aspose.Words for Cloud. Hope, this helps.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
Hi Richard,
Yes, you are right. By default, these parameters are set to false, you need to set them to true to include text areas and footnotes. Our examples team is updating the documentation and all missing examples will be added soon.
Sorry for the inconvenience.
Best Regards,
Hi Muhammad, I’ve tested the parameters and added a PR for the SDK. They seem to work fine, but we’ll do some extra testing.
I’d like to have an extra parameter in the PageStatData for the footnotes, can you make the number of words in footnotes a separate number there?
Hi Richard,
Sorry for the delay. You can set includeFootnotes parameter to true or false to include or exclude footnotes respectively.
Best Regards,
Hi Muhammad, yes we found out that we should include that parameter as true. But my concern is something else:
If we add includeFootnotes as true, please also add the FootnoteCount to each page in the PageStatData.
At the moment when we include the parameter it looks like this:
array:2 [
0 => “with footnotes, with shapes”
1 => {#197
+“WordCount”: 3669
+“ParagraphCount”: 125
+“PageCount”: 12
+“PageStatData”: array:12 [
0 => {#196
+“PageNumber”: 1
+“WordCount”: 337
+“ParagraphCount”: 10
}
but we want it to look like this:
array:2 [
0 => “with footnotes, with shapes”
1 => {#197
+“WordCount”: 3669
+“ParagraphCount”: 125
+“PageCount”: 12
+“FootnoteCount”: 345 // Total words in footnotes
+“PageStatData”: array:12 [
0 => {#196
+“PageNumber”: 1
+“WordCount”: 337
+“ParagraphCount”: 10
+“FootnoteCount”: 38 // Words in footnotes on this page
}
Hi Richard,
A request to enhance PageStatData according to your requirement has been logged into our issue tracking system as WORDSCLOUD-10. We will keep you updated on this issue in this thread.
Best Regards,
Hi Muhammad, thanks for the issue but we think this should be part of the initial release of this ‘footnote’ feature. Given that it already was released, can you give that issue priority?
Hi Richard,
This already has a high priority and you can expect it to be fixed soon.
Best Regards,
Great, thanks for the quick update Muhammad.