+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
(Sorry for the lame reply latency.)
On Jul 18, 2007, at 5:24 PM, Roy T. Fielding wrote:
A system less concerned with backwards compatibility is better off
with a requirement of utf-8, though OS X should have made the filename
encoding a mount option.
I disagree. Having one encoding is
On Aug 6, 2007, at 5:11 PM, Roy T. Fielding wrote:
I agree. But is it the case that non-native mounted filesystems
are name-translated by the kernel? I mean, if OS X did this
consistently
for all mount points, then I would see it as being reasonable for the
OS X applications to reject
On Aug 6, 2007, at 5:39 PM, Wilfredo Sánchez Vega wrote:
On Aug 6, 2007, at 5:11 PM, Roy T. Fielding wrote:
Actually, it also crashes on valid utf-8 in normal form, because OS X
doesn't follow the standard on normalization. See man -s 5 utf8:
If more than a single representation of a
