On 09 Apr 2012, at 11:24 , Watts Martin wrote: > 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?
If the webserver is set to serve UTF-8 pages and you have a page that should be UTF-8 but is encoded in IOS-859-1, strange things can happen. Also, it is not a URI that is the issue, but a link inside an HTML document, and how it is encoded. There is a difference between typing www.åpple.com into a web browser and having an href in an HTML document. > 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." But the browsers ARE smart enough to figure it out. If I type into Safari macupdate.com/web browsers it loads <http://macupdate.com/web%20browsers>, just as it should. -- If the #2 pencil is the most popular, why is it still #2? -- 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>
