On Apr 8, 2012, at 20:06 , LuKreme wrote: > That's 1990's thinking. This 2011 and apps that don't work well and play with > UTF-8 and spaces are simply broken. > > And for the record, I use spaces in filenames all the time and have for 30 > years.
Well, I don't think the question was about apps dealing with filenames, but rather about browsers dealing with URIs, right? To the best of my knowledge, URIs as defined by RFC 3986 require that any character that isn't listed as "reserved" or "unreserved" to always be percent-encoded. That includes spaces, as well as any symbol outside the basic ASCII set. I might use any acceptable filename on a Mac, like "Writing blogging ideas" with spaces and no (visible) extension, but if I was going to put that on a web server, I'd definitely change that to "writing_blogging_ideas.html" to avoid confusion. If I didn't, I'd be relying on browsers and web servers to figure out how to handle those spaces. They probably would, sure -- but most browser will also handle horribly broken HTML. As developers, though, we probably shouldn't just say, "Your browser should be smart enough to figure out what I mean even when I'm violating the spec, because the spec is old and stupid." -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
