Matt, on 19 April 2010 - 05:03 PM, said:
Quote
Matt, on 20 April 2010 - 02:02 AM, said:
Razasharp, on 20 April 2010 - 06:47 AM, said:
Check this out: http://blafoo.net/reallyfunny.htmland then use a newline to keep typing, or even put the URLs into separate lines, with no typing directly afterwards. I think that parsing the links including commas, until the first whitespace is discovered would have less fault rates and more customer satisfaction.
bfarber, on 20 April 2010 - 07:30 AM, said:
I searched http://www.google.com/#hl=en&q=test,but it didn't work
You're still making a presumption, and one which won't always be correct. Note the above link gives two entirely different results whether we parse with or without comma.
Quote
http://www.spiegel.de/wissenschaft/natur/0,1518,689506,00.html, butMaybe a compromise would be to look for "URL delimiters" like html, asp, php, etc. and then allow all commas between the domain and the delimiter or something... I feel there is gotta be a way to make the parser "catch" more exceptions without causing headaches with "the other camp".
Maybe we just need a feature that detects "untagged" URLs and then slams the user in the face with a popup, requiring him to correct his evildoing. That would certainly settle things in the long run...
(Side note: I even fired up my old phpbb installation to check how it handles this, and of course it will parse
http://www.google.com/#hl=en&q=test,but it didn't workwrong, but it parses
http://www.spiegel.de/wissenschaft/natur/0,1518,689506,00.htmlright out of the box.
http://www.spiegel.de/wissenschaft/natur/0,1518,689506,00.html, butis also parsed correctly, the comma is recognized at not being part of the URL.
http://www.spiegel.de/wissenschaft/natur/0,1518,689506,00.html,butfails again.
Just an observation, not comparing or trying to start a religious war here...)




Find content
Male




Posted
