Thanks for the update @asad.ali. Glad to hear that.
Just to reiterate on our expectations from the proposed resetTextSegments method of the TextFragment – we want it to just reset the text segments’ text to an empty string while ensuring that the number of the text segments in the underlying TextSegmentCollection of the TextFragment is left intact.
Thanks
@athota
Sure, we have recorded your concerns and will definitely consider them during feature implementation.
Could you also provide a release timeline for this feature implementation even if tentative ? Would help us plan at our end.
Thanks
@athota
We regret that we cannot provide any ETA or tentative timeline for the ticket to be resolved as it has low priority and will be taken care of on first come first serve basis. However, we have recorded your concerns and will definitely consider them while implementing the feature. As soon as we have any update regarding feature availability, we will share it with you. Please spare us some time.
The ticket is planned to be processed after release of Aspose.PDF for Java 19.7. Once working on the ticket is started, we will be in position to share some expected timeline for this feature to be available. We really appreciate your cooperation and patience and in this matter. Please spare us some time.
We are sorry for the inconvenience.
Hi @asad.ali
Could you please let us know the latest on PDFJAVA-38701 ? Can we expect it’s delivery in this month’s release ?
Thanks
@athota
Investigation is still underway. Please note that required feature needs implementation of new modules and modifications in existing internal components of the API. Hence, the investigation is taking some time. We will let you know as soon as it is completed and share an ETA with you as soon as we have some results. Please spare us little time.
Hi @asad.ali
I see that the status of the linked ticket PDFJAVA-38701 has changed to Feedback. Could you please elaborate on what we can expect ?
Thanks
@athota
The issue status is feedback currently because required feature needs internal implementations and separate tasks have been created for that upon which the main ticket is dependent. Feedback means, this ticket is in waiting queue to get feedback from those internal tasks. As soon as the ticket is resolved, we will let you know. Please spare us little time.
Ok. Thank you.
Hi @asad.ali
It’s been a while since the last update. Could you please provide an update regarding this ?
Thanks
@athota
Thanks for your inquiry.
The earlier logged ticket is still under investigation. As shared earlier, the feature requires changes and new implementations in internal components of the API which makes its nature complex. We will surely let you know as soon as some progress is made towards its implementation. Please spare us little time.
We are sorry for the inconvenience.
The ticket investigation is still underway and we are working over implementing required functionality. However, there are other parallel tasks and implementation which we need to take care of as well. We will surely inform you as soon as we have some certain updates regarding resolution of this ticket. We highly appreciate your patience and cooperation in this matter. Please spare us some time.
We are sorry for the inconvenience.
Hi @asad.ali
Request an update on this. Could you please provide better information as to where we are with addressing this and what we can expect ?
Regards
Aditya
We regret to share that earlier logged ticket has not been yet resolved. We are currently working over implementing fastResetTextSegmentsText method in .NET API and as soon as it is added, we will port it into Java API and share the updated version with you. We are afraid that we are unable to share any reliable ETA due to other high priority implementations and tasks. However, we assure you that we will take care of your concerns and inform you as soon as requested functionality is available. We highly appreciate your patience. Please spare us some time.
We are sorry for the inconvenience.