On Thu, May 12, 2011 at 2:08 AM, Eric U <ericu@google.com> wrote: > Timeless replied: >> no, if the api is case insensitive, then it's case insensitive >> *everywhere*, both on Turkish and on English systems. Things could >> only be case sensitive when serialized to a real file system outside >> of the API. I'm not proposing a case insensitive system which is >> locale aware, i'm proposing one which always folds. > > You're proposing not just a case-insensitive system, but one that forces e.g. an > English locale on all users, even those in a Turkish locale. I don't think > that's an acceptable solution. No, I proposed case preserving. If the file is first created with a dotless i, that hint is preserved and a user agent could and should retain this (e.g. for when it serializes to a real file system). I'm just suggesting not allowing an application to ask for distinct dotted and dotless instances of the same approximate file name. There's a reasonable chance that case collisions will be disastrous when serialized, thus it's better to prevent case collisions when an application tries to create the file - the application can accept a suggested filename or generate a new one.Received on Wednesday, 11 May 2011 23:47:32 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:19 UTC