That way the text with chinese characters will be put in a separate run by MS Word and Aspose.Words will make a separate text segment for it in the xml file with the font correctly set. The workaround is to set the font for far east characters explicitly in MS Word. In MS Word it is Arial Unicode MS.īut unfortunately this attribute is not relayed during transformation. When you type chinese characters in MS Word and the font is set to, for example, Times New Roman then this attribute is implicitly set by MS Word to the name of the font that actually supports far east characters. It corresponds to Font.NameFarEast property in Aspose.Words. MS Word has a special attribute for the text run, which defines what font to use for the characters that belong to Far East languages. I think this is an ordinary problem in CJK. But when save to xml file, ex2 seems to select wrong font (TimeNewRoman not support chinese) and make it empty. In this 2 examples, users see same content and same font in Word application because Word will auto-select right chinese font for “新細明體” in ex2 (I guest!). I save word to xml file like => doc.Save(“doc-1.xml”, SaveFormat.FormatAsposePdf)Īnd trace again and again to find a rule.Įx1 : in word application, if I select chinese font (ex:新細明體) first and input “新細明體”, then the xml tag:segment => 新細明體 => it is correct to translate to PDF file.Įx2 : in word application, if I select font:TimeNewRoman first and input “新細明體”, then the xml tag:segment => 新細明體 => it is wrong and showes empty in PDF file. But there is one problem when chinese fonts content. I am glad to find Aspose product to translate word file to PDF format.
0 kommentar(er)
