Re: Problem in downloading a pdf file having Japanese characters in the name of the file from Jungshik Shin on 2003-11-01 (www-international@w3.org from October to December 2003)

From: Jungshik Shin <jshin@mailaps.org>
Date: Sat, 01 Nov 2003 09:35:54 +0900
To: andrea.vine@Sun.COM
Cc: www-international@w3.org
Message-ID: <3FA2FFEA.4090101@mailaps.org>

A. Vine wrote:
> 
> I'm with Steve.  

On what? I don't think he took any position.

> RFC 2231 is so awkward and has so little support (it's
> been around for many years and yet only now have even a few products 
> decided to support it) 

  It's not more awkward than RFC 2047 for simple cases.

Content-Disposition: attachment; filename*=utf-8''abc%b3%80.txt

Content-Disposition: attachment; filename="=?utf-8?q?abc=b3=80.txt?="

It's not its awkwardness but mostly the ignorance that kept it from
being implemented, IMHO.

> that I never recommend using it.

So, what do you recommend? Using 'raw' UTF-8 chars in http header is 
reasonable  but using 'raw' non-ASCII/non-UTF-8 encodings must be avoided.

Received on Friday, 31 October 2003 19:36:01 UTC