We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Not supported Japanese language Aspose Email for JAVA


i having pst file which having Japanese characters in it
while iterating mail using mapimessage.getBody() giving the proper Japanese characters but mapimessage.getBodyHtml() not giving the proper characters as shown below

mapimessage.getBody() results:

縺ョ縺ッ縲∽ク也阜荳ュ縺ョ菴慕卆荳・ココ縺ョIT邂。逅・€・→繧ウ繝ウ繝斐Η繝シ繧ソ繝ヲ繝シ繧カ繝シ縺ョ逕滓エサ繧貞髄荳翫&縺帙k髱ゥ譁ー逧・↑繧ス繝輔ヨ繧ヲ繧ァ繧「繧「繝励Μ繧ア繝シ繧キ繝ァ繝ウ繧呈署萓帙☆繧九€らァ√◆縺。縺ョ雜ウ霍。縺ェ縺ゥ縲√け繝ゥ繧ヲ繝峨さ繝ウ繝斐Η繝シ繝・ぅ繝ウ繧ー縲ヾharePoint遘サ陦後€・xchange Online縺ョ/繧ェ繝輔ぅ繧ケ365/Google Apps縺ョ繝・・繧ソ邂。逅・€・崕蟄舌Γ繝シ繝ォ縺ョ遘サ陦後€√ョ繝シ繧ソ蠕ゥ譌ァ縲√♀繧医・髮サ蟄舌Γ繝シ繝ォ縺ョ螟画鋤縺ョ繧医≧縺ェ繧「繝ェ繝シ繝翫↓譛€蛻昴↓霑ス蜉縺輔l縺溘b縺ョ縺ァ縺・/div>


mapimessage.getBodyHtml() results:

・・ョ・・ッ・€・・ク・・・・・クュ・・ョ・ス・・・セ・ク・・ココ・・ョIT・ョ。・・・・€・・・ィ・・ウ・・ウ・・・・・・・・シ・・ソ・・ヲ・・シ・・カ・・シ・・ョ・・・・エサ・・・・・・・ク・・・・・・・・・・・・ゥ・・ー・・・・・ェ・・ス・・・・・・・・ヲ・・ァ・・「・・「・・・・・ェ・・ア・・シ・・キ・・ァ・・ウ・・・・・・・セ・・・・・・・・€・・ァ・・・・・・。・・ョ・カウ・キ。・・ェ・・ゥ・€・・・ッ・・ゥ・・ヲ・・・・・ウ・・ウ・・・・・・・・シ・・・・・」・・ウ・・ー・€・SharePoint・ァサ・。・・€・Exchange Online・・ョ/・・ェ・・・・・」・・ケ365/Google Apps・・ョ・・・・・シ・・ソ・ョ。・・・・€・・・サ・ュ・・・。・・シ・・ォ・・ョ・ァサ・。・・€・・・・・・シ・・ソ・セゥ・・ァ・€・・・・・・・・・ウ・・サ・ュ・・・。・・シ・・ォ・・ョ・、・・・・・・ョ・・・・・・・・ェ・・「・・ェ・・シ・・・・・ォ・・€・・・・・ォ・ソス・・・・・・・・・・・・・・・・ョ・・ァ・・・



Any other way to maintain orignal body in html as well as in rtf format?


Thank you for writing to Aspose Support team.

Please share your sample PST file with us that exhibits this behaviour. We’ll look into it for assisting you further.

Hi Kashif

Here the
http://downloads.systoolsgroup.com/installer/Installer_m_link/AllSceneario.zip pst file
which contains,

  • body skipping and formatting issues for some of the mails.
    (what is the significance of getBodyType() because always getting 1)
    ( mapimessage.getBody() - not maintain formatting ,
    mapimessage.getHTMLBody() - sometimes skipping the formatting as well as part of the body
    mapimessage.getBodyRtf() - )
  • date time not accurate (In outlook and mapiMessage.getDeliveryTime() comparison showing differently.)
  • importance field not getting for some of the mails
  • Japanese characters getting correctly in normal text but not in htmlBody

Thanks In advance waiting for your respose


Could you please specify each issue against the messages in the PST file? We have used the latest version of Aspose.Email for .NET 17.6 and were not able to observe the body related issues you have mentioned. Please help us identify each issue you have mentioned against the messages in PST file for further investigation at our end.

actually i’m using Aspose.Email 17.6 for java.


The BodyHtml of the message looks like this due to the encoded Source RTF. As a result, the converted HTML is also encoded as you can see in attached screenshot. This is expected behavior of the API. You can even save the BodyHtml string as some HTML file and open it in browser. It will look fine.

Regarding your other issues, please elaborate each issue one by one (better in a separate thread for each issue) along with some sample screenshots or details for further assistance from our end. We’ll look into these for assisting you further.1.png (46.9 KB)

Not able to view the attached file i.e 1.png (saying server problem at your end while downloading.)
but actually my concern is
we know the solution to use normal text using mapiMessage.getBody() instead of the mapiMessage.HTMLBody()
for this particular scenario but this solution will not working for other mails / as generic solution
means other mails having html/rtf then in that case skipping of formatting from body issue raised

so, you need to provide Body or BodyHtml or BodyRtf separately present for each mail using bodytype
(currently we are getting body type always 1 let me know more significance about int bodytype???)

looking for common solution to fix my concern

Thanks in advance


The RTF and HTML body of the emails always return data in these formats when the source RTF is encoded this way. You need to use getBody() in such case and that is why this is expected behavior of the API. Please refer to 1.png for your kind reference and let us know your feedback.