Hello Aspose Team
Can I get help to know the API to set the default Proofing language in Word document.
I am looking for a set of API’s that will help me to force the language for Spell check (Set Proofing language through the code) to be always set to English.
Thanks in advance !
Regards
-Amit
Hi Amit,
Thanks for your inquiry. We have logged your requirement in our issue tracking system as WORDSNET-13054. Our product team will further look into the details of this problem and we will keep you updated on the status of this issue. We apologize for any inconvenience.
Best regards,
Hello Team
Any quick response Much appreciated !
Regards
-Amit
Hi Amit,
Thanks for your inquiry. Unfortunately, this issue is not resolved yet. This issue is currently pending for analysis and is in the queue. We will inform you via this thread as soon as this issue is resolved. We apologize for any inconvenience.
Best regards,
Hello Aspose Team
May I get a tentative date as to when this issue would be fixed ?
Regards
-Amit
Hi Amit,
Thanks for your inquiry. This issue is currently pending for analysis and in the queue. Unfortunately, at the moment we cannot provide you any reliable estimates. However, you will be notified via this thread as soon as it is resolved. Sorry for any inconvenience.
Best regards,
Hi Amit,
Thanks for being patient. Please check the code below which allows to set the language and the proofing works for it in MS Word:
var doc = new Document();
var db = new DocumentBuilder(doc);
db.Font.LocaleId = 1036;
db.Writeln("Thiss is not US.");
db.Writeln("C'est Francais");
db.Font.LocaleId = 1033;
db.Writeln("Thisss is US");
doc.Save(MyDir + @"16.1.0.docx");
Locale IDs Assigned by Microsoft
If we can help you with anything else, please feel free to ask.
Best regards,
Hello Awais Hafeez
I have already tried couple of below fixes but neither seem to work with my case.
Even after applying the below code fixes the resultant word document when opened in French settings shows the red curvy lines suggesting a spell check.
NodeCollection collection = templateDoc.getChildNodes(NodeType.RUN, true);
for(Run run:collection){
run.getFont().setLocaleId(2057);
}
AND
tempDocBuilder.getFont().setLocaleId(2057);
Regards
-Amit
Hi Amit,
Thanks for your inquiry. Can you please clarify what options/settings you can use in MS Word 2016 to meet your requirement?
Best regards,
Hello Awais Hafeez
I am attaching the image snapshot of word setting…
So although the Aspose API’s are there to enforce the document spell checker to English the word settings still take French as the proofing language.
Regards
-Amit
Hi Amit,
Thanks for the additional information. We have logged your comment in our issue tracking system (against WORDSNET-13054) and will keep you informed of any further proceedings.
Best regards,
Hi Amit,
Please also attach the source document that you used to generate this screenshot. We will investigate the issue further on our end and provide you more information.
Best regards,
Hello Hafeez
As requested please find attached herewith the source document that we used to generate the screenshot that I had sent you previously.
Let us know your feedback on the same.
Regards
-Amit
Hi Amit,
Thanks for sharing the source document. We will inform you via this thread as soon as this issue is resolved.
Best regards,
Hi Amit,
Regarding WORDSNET-13054, can you please run your example on the document using the latest version of Aspose.Words (16.3.0) and see how it goes on your end? We can no longer reproduce it on our end so it would be very helpful to double check with you. Thanks for your cooperation.
Best regards,
Hello,
Can you confirm “WORDSNET-13054” case is not only linked with Aspose API in .NET ? Because we use Java version.
We used currently release R15.4.0 in production system, so use R16.3.0 need a migration to adapt the code.
Can you confirm Aspose can’t deliver a R15.4.1 with this specific fix ?
Sébastien
Hi Sébastien,
Please note that the latest version of Aspose.Words for Java is completely auto-ported from .NET, i.e. we do not write code for Aspose.Words for Java; it is generated out automatically from C# code of Aspose.Words for .NET. In your case, the issue, which was logged with WORDSNET prefix, would be auto resolved for Java variant of Aspose.Words.
Secondly, you’ll need to upgrade to Aspose.Words for Java 16.4.0 from the following link:
https://downloads.aspose.com/words/java
And we do not provide any fixes or patches for old versions of Aspose.Words.
Best regards,
Thx for feedback.
I am surprize about old version management but OK.
Hi Amit,
Regarding WORDSNET-13054, can you please run your example on the document using the latest version of Aspose.Words (16.4.0) and see how it goes on your end? We can no longer reproduce it on our end so it would be very helpful to double check with you. Thanks for your cooperation.
Best regards,
The issues you have found earlier (filed as WORDSNET-13054) have been fixed in this .NET update and this Java update.