-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
word转换成图片排版和office区别很大 #1
Comments
Hi Waydalee, We have reproduced the reported issue with “Shape not wrap properly while converting a Word document to PDF” in our end, and we suspect it to be a defect. We will validate this issue and update you with more details on 27th April 2022. Note: Kindly share the Syncfusion product version used at your end. Regards, |
Hi Waydalee, Currently, we are validating the reported “Shape not wrap properly while converting a Word document to PDF” issue with high priority and will update you with more details on 29th April 2022. Regards, |
Hi Waydalee, We are facing complexity while validating this issue. Currently, we are validating the reported issues with high priority and will update you with more details on 4th May 2022 Regards, |
Hi Waydalee, We have confirmed that the reported issue with “Chinese text is not wrapped properly while converting a Word document to PDF ” is a defect. We will include the fix for this defect in our weekly NuGet release which is estimated to be available on 17th May 2022. The status of this bug can be tracked through the below link: Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.” Regards, |
Hi Waydalee, As promised earlier, we have included the fix for the reported issue with “Chinese text is not wrapped properly while converting a Word document to PDF” in our latest weekly NuGet release (v20.1.0.56). Please use the below link to download our latest weekly NuGet: The status of this bug task can be tracked through the below link: Note: We will include this fix in our 2022 Volume 2 main release which will be available in end of June 2022. Regards, |
No description provided.
The text was updated successfully, but these errors were encountered: