Font scaling problems in word's Conversion

When we use font scaling in font format,It will cause a bad effect in HTML conversion!
You can convert this attach file to HTML!

Hi there,

Thanks for your inquiry. Please note that Aspose.Words mimics the same behavior as MS Word does. If you convert your document to Html using MS Word, you will get the same output.

We have tested the scenario using latest version of Aspose.Words for Java 15.11.0 and have not found the shared issue. Please use Aspose.Words for Java 15.11.0. We have attached the output html with this post for your kind reference.

QQ截图20151229113050.png shows source file in MS-Word,
but when we convert it to html use 15.12.0
it shows QQ截图20151229113307.png

Hi there,

Thanks for your inquiry.

Please note that Aspose.Words mimics the same behavior as MS Word does. To check this behavior, please convert your document to Html using MS Word and Aspose.Words. Open the output Html documents in MS Word and check the output. If you view both output html documents in browser, the output will be same.

Could you convert it to HTML use HtmlFixedSaveOptions?use 15.12.0,you can know what i mean

Hi there,

Thanks for sharing the detail. The shared issue is not related to character scaling. The text ‘放斯蒂芬斯’ overlaps ‘蒂芬’ in output HtmlFixed. We have logged this problem in our issue tracking system as WORDSNET-12896. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

the problem was caused by character scaling,if we scaling with 100%,this problem will not happen!you can solve it by this reason!

Hi there,

Thanks
for sharing the detail. We will inform you via this forum thread once this issue is resolved. Please let us know if you have any more queries.

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

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

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for .NET 18.12 update and this Aspose.Words for Java 18.12 update.