- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 23 Jun 2008 16:21:05 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5773 --- Comment #30 from Julian Reschke <julian.reschke@gmx.de> 2008-06-23 16:21:05 --- (In reply to comment #29) > OK, that makes sense. I didn't think about that. However, two questions? > > 1. is there interoperability problems for UTF-8 percent encoded URL]s as > recommended here: http://www.w3.org/International/O-URL-code.html > 2. is anything being done in the http wg to get http headers updated to unicode > transform or utf-8 specifically? 1: No, I don't think so. 2: The HTTPbis working group is chartered to only clarify HTTP/1.1; unfortunately, this means the defaults for header encoding can not be changed. That being said: RFC2231 already describes how to represent non-ASCII characters in header parameters (as used for C-D); the only problem is that only 2 of the major 4 browsers implement this. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 23 June 2008 16:21:40 UTC