On 10/22/2010 12:30 PM, Dimitri Fontaine wrote:
> Alvaro Herrera<alvherre@commandprompt.com> writes:
>> Excerpts from Dimitri Fontaine's message of vie oct 22 12:25:07 -0300 2010:
>>
>>> Now, if we want to do it the other way round and force extension name to
>>> be the filename, we will have to live with all the restrictions that
>>> filename imposes and that are not the same depending on the OS and the
>>> filesystem, I think, and with systems where we have no way to know what
>>> is the filesystem encoding. Am I wring in thinking that this might be a
>>> problem?
>> I don't see a problem limiting extension names to use only ASCII chars,
>> and a subset of those, at that. They're just names. If you want to get
>> fancy you can use the description.
> So extension names are forced into English? I would live with that, I
> just don't find the answer friendly to the users.
ASCII is not the same thing as English. You can create the names in Pig
Latin or Redneck if you want. It's the charset that's being restricted
here, and we restrict many more things than this to ASCII.
cheers
andrew
