Bug 138239

Summary: Interpret file:// URLs as UTF-8 on non-Windows
Product: WebKit Reporter: Ben Boeckel <mathstuf>
Component: PlatformAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Description Ben Boeckel 2014-10-30 22:32:09 PDT 
Currently, file:// URLs are interpreted using Latin-1 which causes mojibake in directories with utf-8 characters in the filenames. Windows should probably use utf-16 here.
Comment 1 Alexey Proskuryakov 2014-11-02 01:03:21 PST 
Could you please elaborate on how you observe this issue? Is it though WebKit API, or in a browser?

In my experience, file:// URLs are interpreted as utf-8, Safari has no problem dealing with these.
Comment 2 Ben Boeckel 2014-11-02 04:08:42 PST 
Sorry, not the URL itself, but the content at the URL. And yes, in a browser.
Comment 3 Alexey Proskuryakov 2014-11-02 21:44:25 PST 
File-based documents respect default encoding that is set in Safari preferences, so one can change that to UTF-8 if needed.

I don't know how to tell whether UTF-8 is the most common encoding for local plaintext files, but in any case, a web browser is probably not the best application to display those.