[rfc-i] Another example of a draft with non-ASCII characters (draft-ietf-iri-3987bis-12.txt)
Brian E Carpenter
brian.e.carpenter at gmail.com
Tue Jul 17 05:53:42 PDT 2012
On 17/07/2012 13:26, Julian Reschke wrote:
> On 2012-07-17 13:58, Brian E Carpenter wrote:
>>> The text-only version at
>> This works well in Firefox and LibreOffice, but neither Notepad nor
>> can deal with it as far as I can see. I was a bit surprised about Wordpad
>> but I couldn't find a UTF8 setting.
> Notepad works for me (after changing LF to CRLF using unix2dos).
Yes, I told a lie, Notepad gets it right.
It seems that Wordpad handles UTF16 correctly, but not UTF8. If you
do "Save As Unicode" from Notepad, Wordpad can read it, but there are some
unexpected changes of font.
> In general, browsers are supposed to get this right if the charset is
> properly declared on the HTTP response (which it is).
> Once saved to a local file system, it depends on the default of the
> software (fixed encoding? sniffing?). For instance, Notepad AFAIR only
> detects UTF-8 *reliably* when the content starts with a Byte Order Mark.
> Needless to say that these issues go away when you choose a less
> constrained media type where the charset information can be inlined.
> Best regards, Julian
More information about the rfc-interest