Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Unknown <dog@gmail.com>
Newsgroups: comp.os.linux.misc
Subject: Re: How do *nix machos handle M$ problems?
Date: Thu, 17 Mar 2016 09:42:51 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <pan.2016.03.17.19.47.13@gmail.com>
References: <n5i7ap@dont-email.me> <n5k3pncq@news.xmission.com> <4ffdf217fbcdd908d0f1596646de0a24@remailer.privacy.at> <n5n1v4$1dk$1@news.xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 17 Mar 2016 09:42:51 -0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="878ab2efada68a7f7a2b4b004f42f337"; logging-data="19080"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/mCgfhPU/gHZ8BPNvxmdcSdG8sDvnzCU8="
User-Agent: Pan/0.133 (House of Butterflies)
Cancel-Lock: sha1:SORDZ165e3mjIobTkZw4ic3Atcs=
Xref: csiph.com comp.os.linux.misc:17036

On Sat, 26 Dec 2015 21:48:20 +0000, Kenny McCormack wrote:

> In article <4ffdf217fbcdd908d0f1596646de0a24@remailer.privacy.at>,
> Anonymous Remailer (austria) <mixmaster@remailer.privacy.at> ranted and
> raved:
>>
>>Kenny McCormack <gaze...@shell.xmission.com> [KM]: KM>     1) It /is/
>>more restrictive in what are legal filename KM>     characters.  IMHO,
>>the Unix method (of allowing just about KM>     anything) is just plain
>>nuts.
>>
>>If all unix users lived in an english speaking country, then ASCII
>>characters plus a few punctuation marks for filenames might suffice. Now
>>japanese and korean people obviously cannot say the same. The world out
>>there is bigger than what we think and your notion of "legal" does not
>>apply universally... Unicode and its various encodings are the norm for
>>millions of people, who don't share (and don't give a dime about) your
>>view of what is legal.
>>
>>It's a good thing that unix, although invented and first used in the US,
>>does not impose ad-hoc unnecessary restrictions on filenames. Learn how
>>to live with this.
>>
Yes catering for japanese and korean and Arabic, Cyrillic, Hindi ...
via Unicode is great.
But messing ASCII for ENGLISH by replacing the quote with 3 bytes is
ABSURD!!