Status: Untriaged
Owner: ----
CC:
er...@chromium.org
Labels: Type-Bug Pri-2 Area-WebKit OS-Mac Feature-I18N
New issue 125271 by
js...@chromium.org: File uploaded from Mac OS X keeps
its filename in NFD (local file system) instead of NFC form
http://code.google.com/p/chromium/issues/detail?id=125271
Version: 20.0.1115.1 dev
OS: Mac OS 10.6
What steps will reproduce the problem?
1. Create a local file '각.png' on Mac OS X
2. Attach it to a gmail by drag'n'dropping the file to the attachement area
in gmail
3. Go to Linux or Windows
4. Log on to gmail
What is the expected output? What do you see instead?
The file name should be '각.png'
Instead, it's 'ᄀ ᅡ ᆨ.png' (without intervening spaces).
Please use labels and text to provide additional information.
This happens because Mac OS X file system uses Unicode NFD (Normalization
Form Decomposed) while other OS usually expect to see file names in NFC.
While uploading a file, Mac Chrome has to translate NFD on local disk to
NFC. Otherwise, the receiving end (Linux or Windows) would have a surprise
for users.
Note that this is not only for Korean Hangul but for any characters whose
NFD form is different from NFC form. For instance, any Latin letters with
diacritic marks attached will be decomposed.
I thought we had taken care of this on Chrome (A long time ago, Firefox had
a similar problem with the old way of uploading a file :
https://bugzilla.mozilla.org/show_bug.cgi?id=227547 )