[rfc-i] Another example of a draft with non-ASCII characters (draft-ietf-iri-3987bis-12.txt)

"Martin J. Dürst" duerst at it.aoyama.ac.jp
Wed Jul 18 00:47:44 PDT 2012

On 2012/07/17 21:26, Julian Reschke wrote:
> On 2012-07-17 13:58, Brian E Carpenter wrote:
>>> The text-only version at
>>> http://www.sw.it.aoyama.ac.jp/2012/pub/draft-ietf-iri-3987bis-12.utf8.txt
>> This works well in Firefox and LibreOffice, but neither Notepad nor
>> Wordpad
>> 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.

Many thanks everybody for the feedback.

> Notepad works for me (after changing LF to CRLF using unix2dos).

I have fixed this on the server.

> In general, browsers are supposed to get this right if the charset is
> properly declared on the HTTP response (which it is).

Of course. My whole site is UTF-8, except where I need something else 
for testing.

> 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.

I'm reluctant for now to add a BOM, because that might give some 
hick-ups to some kind of processing.

> Needless to say that these issues go away when you choose a less
> constrained media type where the charset information can be inlined.

Yes indeed.

Regards,   Martin.

More information about the rfc-interest mailing list