Changes between Version 5 and Version 6 of ContentDispositionProducerAdvice


Ignore:
Timestamp:
Jul 13, 2011, 7:39:19 PM (8 years ago)
Author:
mnot@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContentDispositionProducerAdvice

    v5 v6  
    2121}}}
    2222
    23 However, when the filename has non-ISO-8859-1 characters in it, it needs to be encoded as described in RFC5987. For example:
     23However, when the filename has non-ASCII characters in it, it needs to be encoded as described in RFC5987. For example:
    2424
    2525{{{
     
    6666
    6767Unfortunately, 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
     72In some cases (e.g., German, which uses many characters from ASCII), this will work fine, because there are reasonable substitution characters.
     73
     74However, consider Japanese, which doesn't share any characters from ASCII.