Changes between Version 5 and Version 6 of ContentDispositionProducerAdvice
- Timestamp:
- 14/07/11 02:39:19 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ContentDispositionProducerAdvice
v5 v6 21 21 }}} 22 22 23 However, when the filename has non- ISO-8859-1characters in it, it needs to be encoded as described in RFC5987. For example:23 However, when the filename has non-ASCII characters in it, it needs to be encoded as described in RFC5987. For example: 24 24 25 25 {{{ … … 66 66 67 67 Unfortunately, there are some UTF-8 characters that look like ISO-8859-1 characters, such as an a with an umlaut (ä). In these cases, some browsers will treat it as UTF-8, even though it's valid ISO-8859-1, causing a loss of interoperability; your users will see the wrong filename. See [http://greenbytes.de/tech/tc2231/#attwithutf8fnplain the test case] for details. 68 69 70 === Why not generate the fallback filename automatically? === 71 72 In some cases (e.g., German, which uses many characters from ASCII), this will work fine, because there are reasonable substitution characters. 73 74 However, consider Japanese, which doesn't share any characters from ASCII.