Re: Accented chars in filenames issue
On 25/06/11 10:16, lee wrote:
> Scott Ferguson <prettyfly.productions@gmail.com> writes:
>
>> I don't think the "no white spaces" and "no accented characters"
>> "rule" is valid in the 21st century. But if some one can put up an
>> authoritative, and recent, reason I'll reconsider.
>
> Since (unfortunately) there isn't anything preventing users from
> creating files with names that contain special characters or spaces, you
> could say that there isn't such a rule anymore.
There is...
>
> Nonetheless I advise against it, very un-authoritatively of course,
> because it can be troublesome to create files with special characters or
> spaces in their names.
>
> To give a silly example, a file named "-rf *" or "rm -rf *"
I defy you to create a file with those name ;-p
NOTE: I've tried. No point in it just being an untested opinion.
> could turn
> out to be disastrous. Using other special characters, for example ä, ü,
> ö, and ß, can give you trouble when locale settings change and may have
> effects that I'm even not aware of.
>
> It's only common sense not to create file names that are likely to yield
> unexpected results.
>
Agreed - but *as it's not possible* my agreement is worthless. It also
belies the point of UTF.
Cheers
--
I'm tired of this back-slapping "Isn't humanity neat?" bullsh#t. We're a
virus with shoes, okay? That's all we are.
~ Bill Hicks
Reply to: