[Webkit-unassigned] [Bug 81270] FileApi does not handle files with NFD encoded umlaut in file name

Wed Mar 21 10:26:57 PDT 2012

https://bugs.webkit.org/show_bug.cgi?id=81270

--- Comment #22 from Eric U. <ericu at chromium.org>  2012-03-21 10:26:57 PST ---
(In reply to comment #20)
> > Is NFD so rare?
> 
> My understanding is that NFD is pretty much limited to OS X. Windows uses precomposed form, and most other systems that became Unicode aware later (including the Web as a whole) naturally leaned towards Windows compatibility.
> 
> I do not know very much about modern Linux though.
> 
> > The kernel just treats strings as bytes
> 
> Sounds like a robust solution would also have to deal with malformed strings (unpaired surrogates etc). I'd prefer if we didn't need to round trip these.

No argument here; I think handling all valid UTF-8 would be sufficient.

> Perhaps a way to hide this issue in practice would be for chromium filesystem code to try a different normalization if a file is not found at first.

That seems a bit slow and error-prone.  It would be pretty easy to attempt to overwrite a file, only to create a new one with the same name but different encoding.  At best, all failing file-open operations would have to be done twice.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.