6 years ago (In reply to Nilesh Deshpande from ) > So according to you UTF-8 encoded characters should not be decoded while > displaying in dialog box(As Mozilla Firefox is doing in this scenario). > Whereas IE and Chrome are displaying Japanese header properly by decoding > and it is wrong? What's wrong is applying percent-decoding to the filename. There is no such thing in the Content-Disposition spec, and IE and Chrome are the only browsers with this bug. > If Mozilla Firefox is correct which encoding format should I use for it? > Is it expected behavior to have garbage/unicode characters on dialog box as > shown in attachment as above (in description)?
Mar 19, 2016 - This can apply to images, pdfs, html, anything a web browser can open (which is. ForceDownload($filename, $type = application/octet-stream). The attachment file name has Japanese characters 'e.g. 金融監督院 rismytesttoZip.zip'.in my program, the file name appears correct in outlook installed on English locale, and the only problem in outlook which installed on Windows with Japanese language only.
6 years ago (In reply to Nilesh Deshpande from ) > >>>What's wrong is applying percent-decoding to the filename. There is no such thing in the Content-Disposition spec, and IE and Chrome are the only browsers with this bug. > Nilesh: What happens is when the download box opens, the title of the box > does not show the valid multi byte name.
It shows%encodechar%encodechar% > like this It shows the value of the filename parameter as sent by the server. It's a server bug to use percent-encoding in a protocol element that does not support it.
> Like I asked earlier can you suggest which encoding form shall we use so > that the file header shows correct file name for multi byte char I already answered that twice.
Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7. Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome.