- From: Frank Ellermann <nobody@xyzzy.claranet.de>
- Date: Tue, 25 Mar 2008 12:40:53 +0100
- To: ietf-http-wg@w3.org
Mark Nottingham wrote: > remove the requirement that only RFC2047 encoding be used; > instead, recommend that context-specific encoding rules be > used (giving examples), and failing that, the \u'nnnnnn' > form from BCP137. Are you sure that you want more than one way (MIME) for this magic, and if yes, are you sure that \u'nnnnnn' is the right way in HTTP ? If there is a chance that these values have to be displayed in HTML pages or used in XML files the NCR form &#xnnnnnn; might work "as is", for \u'nnnnnn' something needs to determine a corresponding UTF-16, hex. NCR, or UTF-8. Frank
Received on Tuesday, 25 March 2008 11:39:14 UTC