Thanks for your advice. I’m aware of such settings but I don’t think this would work in this case.
First thing is that the document is opened in English settings in Office Word, not in French, when I converted this to PDF using Word ‘save as’ feature, it is using English local but could still produce the french date format. So I don’t think the date field region should rely on the document/application level.
Second is that if I set such settings in Aspose, all date fields will use the french setting, but in fact in Word you might have date from different regions. If I set such setting in Aspose, the result will all be changed to French. I have attached a test file and a screenshot for your reference
testmultilanguage.zip (36.6 KB)
image.png (134.2 KB)
Since Aspose.Words mimics the features in Word, it should have the same ability to judge each field separately without changing the thread locale, otherwise it is not possible to fully reflect the content in MS Word.
UPDATE: in case it helps, I’m also adding here why the French language is individually set on the field level: the style of the specific run has French region. I’ve highlighted such settings in the below screenshot.
image.png (441.1 KB)
therefore, setting up a French thread will not help the issue but overwrite the language settings in every other run which might very likely be some other languages.
Could this be fixed so Aspose would properly render content based on the correct locale of each run?