Ohm Sign Symbol font name is changed after using 'com.aspose.words.Document'

Aspose.Words Product Family
1

Hi,

I find that after using class ‘com.aspose.words.Document’ to update the MS Word docx document, the font name of the ‘Ohm Sign’ symbol is changed to ‘Times New Roman’ automatically, so that such symbol become ‘invisible’ when open it.

Here is the code I try to insert a blank line at the end of original document.

Document srcDoc = new Document(“C:\in.docx”);
DocumentBuilder srcBuilder = new DocumentBuilder(srcDoc);
srcBuilder.moveToDocumentEnd();
srcBuilder.writeln();
srcDoc.save(“C:\out.docx”);

Here is the part of ‘word\document.xml’ after unzip “in.docx”:
<w:r>
<w:rPr><w:rFonts w:hint=“eastAsia”/></w:rPr>
<w:sym w:font=“Symbol” w:char=“F06D”/>
</w:r>

Here is the part of ‘word\document.xml’ after unzip “out.docx”:
<w:r>
<w:rPr><w:rFonts w:ascii=“Times New Roman” w:hAnsi=“Times New Roman” w:hint=“eastAsia” /></w:rPr>
<w:sym w:font=“Times New Roman” w:char=“F06D” />
</w:r>

Can you help? How to avoid this problem?

Regards
Laurence

2
Hi Laurence,

Thanks for your inquiry. Could you please attach your input Word document and output Word document showing the undesired behavior here for testing? We will investigate the issue on our end and provide you more information.

Best regards,
3

Hi,

Here is the code:

Document srcDoc = new Document(“C:\TEMP\ASPOSE\ELE23.5.docx”);
DocumentBuilder srcBuilder = new DocumentBuilder(srcDoc);
srcBuilder.moveToDocumentEnd();
srcBuilder.writeln();
srcDoc.save(“C:\TEMP\ASPOSE\ELE23.5-output.docx”);

and the result are attached. Looking forward for your reply.

Regards
Laurence

4

Hi Laurence,


Thanks for the additional information. While using the latest version of Aspose.Words i.e. 14.11.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-11234. Your request has also been linked to the appropriate issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
5

Hi

May I know the target release date for this issue? As we need to resolve this problem before launching our application to production. Please help.

Regards
Laurence

6
Hi Laurence,

Thanks for your inquiry. Unfortunately, this issue is not resolved yet. Currently, it is pending for analysis and is in the queue. Also, at the moment we can't provide you the ETA for this issue. However, we will inform you via this thread as soon as it is resolved. Sorry for the inconvenience.

Best regards,
7

Hi Support,



Any hints that this issue will be fixed?


Regards,
Laurence
8

Hi Laurence,


Thanks for your inquiry. Unfortunately, your issue is not resolved yet. We have asked the ETA of this issue from our product team and will update you as soon as any estimates are available. We apologize for your inconvenience.

Best regards,
9

Will the issue going to be resolved after 2 years?

10
Hi Laurence,

Thanks for your inquiry and sorry for the delay. We are no longer able to reproduce this issue on our end (see attachment). Please upgrade to the latest version i.e. Aspose.Words for .NET 16.10.0. Hope, this helps.
http://www.aspose.com/downloads/words/net

Best regards,
11

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

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