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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 21 09:57:56 PDT 2012


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





--- Comment #17 from Eric U. <ericu at chromium.org>  2012-03-21 09:57:55 PST ---
(In reply to comment #16)
> This sounds more like a Linux file system issue than anything else. Are all Linux file systems like this, or just some of them? This can be seen as a configuration issue - users that want Unicode in file names to work should use a Unicode aware file system.
> 
> > The user could also just plug in a USB drive with denormalized paths on it
> 
> Is this a practical scenario? How would they get non-NFC paths on the USB drive?

Is NFD so rare?  The ChromeOS bug [http://code.google.com/p/chromium-os/issues/detail?id=26028] has multiple reports from different users and several different sources of paths.  Granted, several were from screen captures, so there's probably a single screencapture app that's causing 2-3 of the reports, but there were other sources as well.

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



More information about the webkit-unassigned mailing list